[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121002125819.GY4360@opensource.wolfsonmicro.com>
Date: Tue, 2 Oct 2012 13:58:20 +0100
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Felipe Balbi <balbi@...com>
Cc: "ABRAHAM, KISHON VIJAY" <kishon@...com>,
Sourav Poddar <sourav.poddar@...com>,
devicetree-discuss@...ts.ozlabs.org,
linux-arm-kernel@...ts.infradead.org, linux-omap@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-input@...r.kernel.org,
b-cousson@...com, santosh.shilimkar@...com, sameo@...ux.intel.com
Subject: Re: [PATCHv3 1/4] mfd: smsc: Add support for smsc gpio io/keypad
driver
On Tue, Oct 02, 2012 at 03:43:22PM +0300, Felipe Balbi wrote:
> BTW, OTOH writing all children into the DT actually describes the HW,
> no ? And depending on the device I feel it'd be better to write that
Well, it depends on the hardware. Some hardware has a bunch of nice,
neat IPs which can usefully be reproduced and which map sensibly onto OS
abstractions but a lot of it doesn't and frequently the abstractions
which Linux wants to use don't bear a huge resemblance to the hardware
(and Linux's ideas can change over time, as with the clock API being
factored out for example).
> data to DT. Think of twlxxxx (TI's PMICs), we might have completely
> unrelated drivers using one of TWL's GPIO lines as an interrupt source.
> If that particular children isn't listed in DT, it can't be used as an
> interrupt-parent, right ?
You can have the interrupt controller there without having to list every
IP in the device, just make the parent device the interrupt controller
to DT.
--
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