[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <FE853F2C-A85A-4D0E-BF0E-80698F3E6567@jcrosoft.com>
Date: Wed, 13 Mar 2013 04:24:20 +0800
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@...osoft.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@...osoft.com>,
Johan Hovold <jhovold@...il.com>,
Evgeniy Polyakov <zbr@...emap.net>,
Nicolas Ferre <nicolas.ferre@...el.com>,
Imre Kaloz <kaloz@...nwrt.org>,
Krzysztof Halasa <khc@...waw.pl>,
Eric Miao <eric.y.miao@...il.com>,
Haojian Zhuang <haojian.zhuang@...il.com>,
Daniel Mack <zonque@...il.com>,
Ville Syrjälä <syrjala@....fi>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
stable <stable@...r.kernel.org>
Subject: Re: [PATCH] ARM: w1-gpio: fix erroneous gpio requests
On Mar 13, 2013, at 4:20 AM, Greg Kroah-Hartman <gregkh@...uxfoundation.org> wrote:
> On Tue, Mar 12, 2013 at 08:21:34PM +0100, Johan Hovold wrote:
>> Fix regression introduced by commit d2323cf773 ("onewire: w1-gpio: add
>> ext_pullup_enable pin in platform data") which added a gpio entry to the
>> platform data, but did not add the required initialisers to the board
>> files using it. Consequently, the driver would request gpio 0 at probe,
>> which could break other uses of the corresponding pin.
>>
>> On AT91 requesting gpio 0 changes the pin muxing for PIOA0, which, for
>> instance, breaks SPI0 on at91sam9g20.
not only on AT91, 0 is a valid gpio
>>
>> Cc: stable <stable@...r.kernel.org>
>> Signed-off-by: Johan Hovold <jhovold@...il.com>
>> ---
>>
>> Not sure whose tree this should go in through, so adding relevant maintainers
>> and authors as CC.
>
> As I took the offending patch, I might as well take this fix for it as
> well.
>
> Unless anyone else objects?
Acked-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@...osoft.com>
Best Regards,
J.
--
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