The ARCH_MX* and MACH_MX* macros a scheduled for removal for
longer. This series removes several of them in drivers/
Sascha Hauer (5):
mmc i.MX: remove individual SoC dependency
dma i.MX: remove individual SOC dependency
USB host i.MX21: remove dependency on MACH_MX21
USB gadget i.MX1: remove dependency on ARCH_MXC
media i.MX1 camera: remove dependency on ARCH_MX1
drivers/dma/Kconfig | 6 +++---
drivers/media/video/Kconfig | 2 +-
drivers/mmc/host/Kconfig | 12 ++++++------
drivers/usb/gadget/Kconfig | 9 ++++-----
drivers/usb/host/Kconfig | 6 +++---
5 files changed, 17 insertions(+), 18 deletions(-)
The individual SoC dependency in Kconfig hardly scales anymore.
Instead of having such a fine grained dependency just depend
on ARCH_MXC and risk that the uninformed user has to look in
the help text to figure out which driver is the correct one.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Chris Ball <redacted>
Cc: linux-mmc at vger.kernel.org
---
drivers/mmc/host/Kconfig | 12 ++++++------
1 files changed, 6 insertions(+), 6 deletions(-)
The individual SoC dependency in Kconfig hardly scales anymore.
Instead of having such a fine grained dependency just depend
on ARCH_MXC and risk that the uninformed user has to look in
the help text to figure out which driver is the correct one.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Vinod Koul <redacted>
---
drivers/dma/Kconfig | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
the MACH_MX* macros are scheduled for removal, so just depend
on ARCH_MXC instead. The Kconfig text makes it clear on which
SoC the driver runs on.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Cc: linux-usb at vger.kernel.org
---
drivers/usb/host/Kconfig | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
The ARCH_MX1 scheduled for removal. Instead, depend on ARCH_MXC
and make clear in the Kconfig text that only i.MX1 has this
hardware.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Cc: linux-usb at vger.kernel.org
---
drivers/usb/gadget/Kconfig | 9 ++++-----
1 files changed, 4 insertions(+), 5 deletions(-)
The ARCH_MX1 macro is scheduled for removal. Instead,
depend on ARCH_MXC. The Kconfig text makes it clear
on which SoC rhis driver runs on.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
drivers/media/video/Kconfig | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
Vinod,
Ping. Can you please queue this one?
Thanks
Sascha
On Wed, Aug 24, 2011 at 08:41:09AM +0200, Sascha Hauer wrote:
quoted hunk
The individual SoC dependency in Kconfig hardly scales anymore.
Instead of having such a fine grained dependency just depend
on ARCH_MXC and risk that the uninformed user has to look in
the help text to figure out which driver is the correct one.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Vinod Koul <redacted>
---
drivers/dma/Kconfig | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
--
1.7.5.4
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
On Tue, 2011-11-08 at 16:22 +0100, Sascha Hauer wrote:
Vinod,
Ping. Can you please queue this one?
Sorry Sascha, looks like I have missed this one :(
Nevertheless, this seems to be part of a series, but I couldn't locate
the rest.
Do you want me to apply only this individual patch, seems little odd if
thats the case...
Thanks
Sascha
On Wed, Aug 24, 2011 at 08:41:09AM +0200, Sascha Hauer wrote:
quoted
The individual SoC dependency in Kconfig hardly scales anymore.
Instead of having such a fine grained dependency just depend
on ARCH_MXC and risk that the uninformed user has to look in
the help text to figure out which driver is the correct one.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Vinod Koul <redacted>
---
drivers/dma/Kconfig | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
--
1.7.5.4
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
On Tue, Nov 08, 2011 at 09:40:33PM +0530, Vinod Koul wrote:
On Tue, 2011-11-08 at 16:22 +0100, Sascha Hauer wrote:
quoted
Vinod,
Ping. Can you please queue this one?
Sorry Sascha, looks like I have missed this one :(
Nevertheless, this seems to be part of a series, but I couldn't locate
the rest.
Do you want me to apply only this individual patch, seems little odd if
thats the case...
It was part of a series that removes SOC dependencies in different
subsystems. So it's right that each patch goes via a different
maintainer.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
From: Michał Mirosław <hidden> Date: 2011-11-08 20:42:56
2011/8/24 Sascha Hauer [off-list ref]:
The individual SoC dependency in Kconfig hardly scales anymore.
Instead of having such a fine grained dependency just depend
on ARCH_MXC and risk that the uninformed user has to look in
the help text to figure out which driver is the correct one.
[...]
?config MX3_IPU
? ? ? ?bool "MX3x Image Processing Unit support"
- ? ? ? depends on ARCH_MX3
+ ? ? ? depends on ARCH_MXC
? ? ? ?select DMA_ENGINE
? ? ? ?default y
? ? ? ?help
You could instead make it depend on HAVE_MX3_IPU and select this
symbol from relevant model config. Leaving it for the users is making
every one of them redo the work you already did.
Best Regards,
Micha? Miros?aw
On Tue, Nov 08, 2011 at 09:42:56PM +0100, Micha? Miros?aw wrote:
2011/8/24 Sascha Hauer [off-list ref]:
quoted
The individual SoC dependency in Kconfig hardly scales anymore.
Instead of having such a fine grained dependency just depend
on ARCH_MXC and risk that the uninformed user has to look in
the help text to figure out which driver is the correct one.
[...]
quoted
?config MX3_IPU
? ? ? ?bool "MX3x Image Processing Unit support"
- ? ? ? depends on ARCH_MX3
+ ? ? ? depends on ARCH_MXC
? ? ? ?select DMA_ENGINE
? ? ? ?default y
? ? ? ?help
You could instead make it depend on HAVE_MX3_IPU and select this
symbol from relevant model config. Leaving it for the users is making
every one of them redo the work you already did.
I thought about this. I came to the conclusion that these are quite hard
to change when they are present in many subsystems (I try to get rid of
ARCH_MXx macros for some time now). Also with upcoming devicetree
support the IMX_HAVE_ macros will loose their meaning anyway. Being a
bit more relaxed with the 'depends on' only means that a user might
compile in some unused drivers, which is the standard case on other
architectures like x86 anyway.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
On Tue, Nov 08, 2011 at 09:40:33PM +0530, Vinod Koul wrote:
On Tue, 2011-11-08 at 16:22 +0100, Sascha Hauer wrote:
quoted
Vinod,
Ping. Can you please queue this one?
Sorry Sascha, looks like I have missed this one :(
Nevertheless, this seems to be part of a series, but I couldn't locate
the rest.
Do you want me to apply only this individual patch, seems little odd if
thats the case...
Yes, only this patch please. Maybe I should send patches for different
subsystems in individual patches instead as a series, but it's very
convenient to create a series, add maintainers to the Cc field and just
send it out.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |