On 23/03/2020 21.45, Tom Rini wrote:
> On Mon, Mar 23, 2020 at 01:13:01AM +0100, Rasmus Villemoes wrote:
>> On 03/03/2020 13.19, Rasmus Villemoes wrote:
>>> On 28/01/2020 13.04, Rasmus Villemoes wrote:
[resending with Mario's correct address, sorry for the double post]
The driver cor
On Mon, Mar 23, 2020 at 01:13:01AM +0100, Rasmus Villemoes wrote:
> On 03/03/2020 13.19, Rasmus Villemoes wrote:
> > On 28/01/2020 13.04, Rasmus Villemoes wrote:
> >> [resending with Mario's correct address, sorry for the double post]
> >>
> >> The driver correctly uses the shadow register when ask
On 03/03/2020 13.19, Rasmus Villemoes wrote:
> On 28/01/2020 13.04, Rasmus Villemoes wrote:
>> [resending with Mario's correct address, sorry for the double post]
>>
>> The driver correctly uses the shadow register when asked for the
>> current value of an output gpio. Unfortunately, it does RMW on
On 28/01/2020 13.04, Rasmus Villemoes wrote:
> [resending with Mario's correct address, sorry for the double post]
>
> The driver correctly uses the shadow register when asked for the
> current value of an output gpio. Unfortunately, it does RMW on the
> gpdat register both when setting a gpio as
On 28/01/2020 13.04, Rasmus Villemoes wrote:
> Rasmus Villemoes (2):
> gpio: mpc8xxx: don't modify gpdat when setting gpio as input
> gpio: mpc8xxx: don't do RMW on gpdat register when setting value
>
> drivers/gpio/mpc8xxx_gpio.c | 41 ++---
> 1 file changed,
[resending with Mario's correct address, sorry for the double post]
The driver correctly uses the shadow register when asked for the
current value of an output gpio. Unfortunately, it does RMW on the
gpdat register both when setting a gpio as input and output. These two
patches fix that.
Aside: A
6 matches
Mail list logo