On Feb 28, 2014, at 5:18 PM, Santosh Shilimkar <santosh.shilimkar@xxxxxx> wrote: > Based on earlier thread "https://lkml.org/lkml/2013/10/7/662"; and > further discussion at Kernel Summit'2013, it was agreed to create > 'driver/soc' for drivers which are quite SOC specific. > > Lets take the discussion forward with this patch. > > Cc: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> > Cc: Kumar Gala <galak@xxxxxxxxxxxxxx> > Cc: Paul Walmsley <paul@xxxxxxxxx> > Cc: Olof Johansson <olof@xxxxxxxxx> > Cc: Arnd Bergmann <arnd@xxxxxxxx> > Signed-off-by: Sandeep Nair <sandeep_n@xxxxxx> > Signed-off-by: Santosh Shilimkar <santosh.shilimkar@xxxxxx> > --- > drivers/Kconfig | 2 ++ > drivers/Makefile | 4 ++++ > drivers/soc/Kconfig | 3 +++ > 3 files changed, 9 insertions(+) > create mode 100644 drivers/soc/Kconfig > > diff --git a/drivers/Kconfig b/drivers/Kconfig > index b3138fb..37f955f 100644 > --- a/drivers/Kconfig > +++ b/drivers/Kconfig > @@ -130,6 +130,8 @@ source "drivers/staging/Kconfig" > > source "drivers/platform/Kconfig" > > +source "drivers/soc/Kconfig" > + > source "drivers/clk/Kconfig" > > source "drivers/hwspinlock/Kconfig" > diff --git a/drivers/Makefile b/drivers/Makefile > index 8e3b8b0..0d8e2a4 100644 > --- a/drivers/Makefile > +++ b/drivers/Makefile > @@ -132,6 +132,10 @@ obj-$(CONFIG_VHOST_RING) += vhost/ > obj-$(CONFIG_VLYNQ) += vlynq/ > obj-$(CONFIG_STAGING) += staging/ > obj-y += platform/ > + > +# SOC specific drivers > +obj-y += soc/ > + > #common clk code > obj-y += clk/ > > diff --git a/drivers/soc/Kconfig b/drivers/soc/Kconfig > new file mode 100644 > index 0000000..2f9d7d0 > --- /dev/null > +++ b/drivers/soc/Kconfig > @@ -0,0 +1,3 @@ > +menu "SOC specific Drivers" > + > +endmenu > -- > 1.7.9.5 Is there a follow up patch that populates this with something real? - k -- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
