[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140908113547.GJ4015@sirena.org.uk>
Date: Mon, 8 Sep 2014 12:35:47 +0100
From: Mark Brown <broonie@...nel.org>
To: Anders Berg <anders.berg@...gotech.com>
Cc: Linus Walleij <linus.walleij@...aro.org>,
"linux-spi@...r.kernel.org" <linux-spi@...r.kernel.org>,
Alexandre Courbot <gnurou@...il.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] gpio: Add driver for AXM55xx SSP chip selects
On Mon, Sep 08, 2014 at 01:02:32PM +0200, Anders Berg wrote:
> On Sat, Sep 6, 2014 at 3:53 PM, Mark Brown <broonie@...nel.org> wrote:
> > Would it not be more straightforward to just register it as a platform
> > device in this case, or use a separate OF ID in the DT? We appear to
> > specify a compatible string when registering AMBA devices even if we are
> > capable of identifying using the ID registers.
> I'll drop this gpio patch for now and submit a patch on the pl022
> driver instead. I read the arm,primecell binding and learned that
> there is a property (arm,primecell-periphid) that can be used to
> override the HW PrimeCell ID. Seems like something to use here, right?
Possibly, though if there's no hardware ID to override to that might not
be the best option. You could always define a property that's specific
to the pl022 driver flagging that it's got these extra chip selects though.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists