[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE0=X_3QO5p26M=FS7joKS3zD6LAM_moFutHNcyE1-CjauL3Rw@mail.gmail.com>
Date: Fri, 5 Sep 2014 11:05:37 +0200
From: Anders Berg <anders.berg@...gotech.com>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Mark Brown <broonie@...nel.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 Thu, Sep 4, 2014 at 7:06 PM, Mark Brown <broonie@...nel.org> wrote:
>> On Thu, Sep 04, 2014 at 07:04:44PM +0200, Linus Walleij wrote:
>>> I need an ACK from Mark Brown on this before I apply.
>>> The driver seems to do what it should, but I need Mark to
>>> be OK with exporting the CS signals from an SSP/SPI block
>>> to be exposed to Linux as GPIOs.
>>>
>>> (Top-posting and quoting patch verbatim so Mark gets it.)
>>
>> I don't see any sort of reasoning for this?
>
> Maybe there was some earlier, but this is an excellent opportunity
> to repeat it... So Anders: why do you want to do this?
>
Well, the problem with adding this to the spi-pl022 driver (as a
vendor specific extension) is that this IP block unfortunately isn't
distinguishable from the standard ARM PL022 implementation (same
values in the PrimeCell identification registers). That's why I went
down the GPIO path...
/Anders
--
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