From: Sinan Akman <sinan@writeme.com>
To: "J. Neuschäfer" <j.ne@posteo.net>, "Sinan Akman" <sinan@writeme.com>
Cc: Mario Six <mario.six@gdsys.cc>, Tom Rini <trini@konsulko.com>,
u-boot@lists.denx.de
Subject: Re: [PATCH 4/4] gpio: mpc8xxx: Preserve pre-init state of outputs
Date: Thu, 19 Dec 2024 11:13:41 -0500 [thread overview]
Message-ID: <08d47536-b375-4524-bb2c-8ecfdeff8bbd@writeme.com> (raw)
In-Reply-To: <Z2Qac5yDvhhJV8Pu@probook>
On 2024-12-19 08:06, J. Neuschäfer wrote:
> On Wed, Dec 18, 2024 at 02:20:21PM -0500, Sinan Akman wrote:
>> Hi
>>
>> On 2024-12-15 10:18, J. Neuschäfer via B4 Relay wrote:
>>> From: "J. Neuschäfer"<j.ne@posteo.net>
>>>
>>> The mpc8xxx_gpio driver contains a workaround for certain chips
>>> where the previously written state of outputs cannot be read back
>>> from the GPIO data (GPDAT) register (MPC8572/MPC8536). This workaround
>>> consists of tracking the state of GPDAT in a "shadow register" (i.e. a
>>> software variable). The shadow register is initialized to zero.
>>>
>>> This results in a problem w.r.t. outputs that are configured to a
>>> high (1) state before U-Boot runs, but not touched by U-Boot itself:
>>> Due to the zero-initialization, these GPIOs end up being set to zero,
>>> the first time that any other output is set.
>>>
>>> To avoid such issues initialize the GPDAT shadow register to the value
>>> previously held by any outputs, if possible. On MPC8572/MPC8536 this
>>> should make no difference,
>>
>> Did you test this on a MPC83xx board ?
>
> Yes, on MPC8314E. I'll mention it in the commit message.
yes please do, thanks.
Reviewed-by: Sinan Akman <sinan@writeme.com>
>
> I did not test it on MPC85xx, though.
>
>
> -- jn
next prev parent reply other threads:[~2024-12-19 16:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-15 15:18 [PATCH 0/4] Misc. PowerPC MPC83xx fixes/cleanups J. Neuschäfer via B4 Relay
2024-12-15 15:18 ` [PATCH 1/4] powerpc: mpc83xx: Fix timer value calculation J. Neuschäfer via B4 Relay
2024-12-18 19:24 ` Sinan Akman
2024-12-15 15:18 ` [PATCH 2/4] powerpc: mpc83xx: Allow including initreg.h into multiple files J. Neuschäfer via B4 Relay
2024-12-18 19:18 ` Sinan Akman
2024-12-19 12:55 ` J. Neuschäfer
2024-12-19 16:16 ` Sinan Akman
2024-12-15 15:18 ` [PATCH 3/4] powerpc: mpc83xx: Use defined constant for SPCR[TBEN] J. Neuschäfer via B4 Relay
2024-12-18 19:25 ` Sinan Akman
2024-12-15 15:18 ` [PATCH 4/4] gpio: mpc8xxx: Preserve pre-init state of outputs J. Neuschäfer via B4 Relay
2024-12-18 19:20 ` Sinan Akman
2024-12-19 13:06 ` J. Neuschäfer
2024-12-19 16:13 ` Sinan Akman [this message]
2024-12-15 18:03 ` [PATCH 0/4] Misc. PowerPC MPC83xx fixes/cleanups Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=08d47536-b375-4524-bb2c-8ecfdeff8bbd@writeme.com \
--to=sinan@writeme.com \
--cc=j.ne@posteo.net \
--cc=mario.six@gdsys.cc \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox