[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <379B16EC-BFAA-4C27-8321-E7133C03368D@antoniou-consulting.com>
Date: Mon, 7 Jan 2013 22:13:30 +0200
From: Pantelis Antoniou <panto@...oniou-consulting.com>
To: Tony Lindgren <tony@...mide.com>
Cc: Grant Likely <grant.likely@...retlab.ca>,
Rob Herring <rob.herring@...xeda.com>,
Rob Landley <rob@...dley.net>, Jon Loeliger <jdl@....com>,
Stephen Warren <swarren@...dotorg.org>,
David Gibson <david@...son.dropbear.id.au>,
Benoit Cousson <b-cousson@...com>,
Mitch Bradley <wmb@...mworks.com>,
Alan Tull <atull@...era.com>, Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-omap@...r.kernel.org, devicetree-discuss@...ts.ozlabs.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
Matt Porter <mporter@...com>, Russ Dill <Russ.Dill@...com>,
Koen Kooi <koen@...inion.thruhere.net>,
Joel A Fernandes <agnel.joel@...il.com>,
Rob Clark <robdclark@...il.com>,
Jason Kridner <jkridner@...gleboard.org>,
Matt Ranostay <mranostay@...il.com>
Subject: Re: [PATCH 1/5] capemgr: Beaglebone DT overlay based cape manager
Hi Tony,
On Jan 7, 2013, at 10:09 PM, Tony Lindgren wrote:
> * Pantelis Antoniou <panto@...oniou-consulting.com> [130107 10:54]:
>> A cape loader based on DT overlays and DT objects.
>>
>> Beaglebone cape manager implementation.
>>
>> Signed-off-by: Pantelis Antoniou <panto@...oniou-consulting.com>
>> ---
>> arch/arm/mach-omap2/Kconfig | 2 +
>> drivers/misc/Kconfig | 2 +
>> drivers/misc/Makefile | 1 +
>> drivers/misc/cape/Kconfig | 5 +
>> drivers/misc/cape/Makefile | 5 +
>> drivers/misc/cape/beaglebone/Kconfig | 11 +
>> drivers/misc/cape/beaglebone/Makefile | 5 +
>> drivers/misc/cape/beaglebone/capemgr.c | 1835 ++++++++++++++++++++++++++++++++
>
> The driver should probably be in drivers/bus?
>
It was a bus on the previous iteration and there was a flame storm of epic proportions.
It is not a bus at all now, it's just a device loader; there are no
bus constructs at all. I am at a loss to classify it really, so drivers/misc
where every misfit ends up sounded OK.
I'm open to suggestions though.
>> 8 files changed, 1866 insertions(+)
>> create mode 100644 drivers/misc/cape/Kconfig
>> create mode 100644 drivers/misc/cape/Makefile
>> create mode 100644 drivers/misc/cape/beaglebone/Kconfig
>> create mode 100644 drivers/misc/cape/beaglebone/Makefile
>> create mode 100644 drivers/misc/cape/beaglebone/capemgr.c
>>
>> diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig
>> index 41b581f..f0c2eab 100644
>> --- a/arch/arm/mach-omap2/Kconfig
>> +++ b/arch/arm/mach-omap2/Kconfig
>> @@ -18,6 +18,8 @@ config ARCH_OMAP2PLUS_TYPICAL
>> select TWL4030_CORE if ARCH_OMAP3 || ARCH_OMAP4
>> select TWL4030_POWER if ARCH_OMAP3 || ARCH_OMAP4
>> select VFP
>> + select OF_OVERLAY
>> + select OF_RESOLVE
>> help
>> Compile a kernel suitable for booting most boards
>
> You should just make the driver depend on OF_OVERLAY and
> OF_RESOLVE as most SoCs won't need this. Then we can select
> it in the omap2plus_defconfig.
>
OK
> Regards,
>
> Tony
Regards
-- Pantelis
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists