On Thu, May 02, 2019 at 02:38:14AM +0300, Dmitry Osipenko wrote: > In order to reflect that driver serves NVIDIA Tegra30 and later SoC > generations, let's rename the driver's source file to "tegra30-devfreq.c". > This will make driver files to look more consistent after addition of a > driver for Tegra20. > > Reviewed-by: Chanwoo Choi <[email protected]> > Signed-off-by: Dmitry Osipenko <[email protected]> > --- > drivers/devfreq/Makefile | 2 +- > drivers/devfreq/{tegra-devfreq.c => tegra30-devfreq.c} | 0 > 2 files changed, 1 insertion(+), 1 deletion(-) > rename drivers/devfreq/{tegra-devfreq.c => tegra30-devfreq.c} (100%) > > diff --git a/drivers/devfreq/Makefile b/drivers/devfreq/Makefile > index 32b8d4d3f12c..47e5aeeebfd1 100644 > --- a/drivers/devfreq/Makefile > +++ b/drivers/devfreq/Makefile > @@ -10,7 +10,7 @@ obj-$(CONFIG_DEVFREQ_GOV_PASSIVE) += governor_passive.o > # DEVFREQ Drivers > obj-$(CONFIG_ARM_EXYNOS_BUS_DEVFREQ) += exynos-bus.o > obj-$(CONFIG_ARM_RK3399_DMC_DEVFREQ) += rk3399_dmc.o > -obj-$(CONFIG_ARM_TEGRA_DEVFREQ) += tegra-devfreq.o > +obj-$(CONFIG_ARM_TEGRA_DEVFREQ) += tegra30-devfreq.o
Technically this changes the name of the driver. Sometimes boot or other
scripts rely on those names. Perhaps a better way of keeping backwards-
compatibility would be to do:
obj-$(CONFIG_ARM_TEGRA_DEVFREQ) += tegra-devfreq.o
tegra-devfreq-y += tegra30-devfreq.o
That way you can later on just add the tegra20-devfreq.o to that driver
as well and have them both ship in one .ko.
Thierry
>
> # DEVFREQ Event Drivers
> obj-$(CONFIG_PM_DEVFREQ_EVENT) += event/
> diff --git a/drivers/devfreq/tegra-devfreq.c
> b/drivers/devfreq/tegra30-devfreq.c
> similarity index 100%
> rename from drivers/devfreq/tegra-devfreq.c
> rename to drivers/devfreq/tegra30-devfreq.c
> --
> 2.21.0
>
signature.asc
Description: PGP signature
