From: Tom Rini <trini@konsulko.com>
To: Stefan Bosch <stefan_b@posteo.net>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH v1] arm: dts: s5p4418: fix "mmc write failed" e.g. at cmd saveenv
Date: Wed, 8 Apr 2026 12:05:49 -0600 [thread overview]
Message-ID: <20260408180549.GL41863@bill-the-cat> (raw)
In-Reply-To: <cb9de6df-ea93-6c7e-211a-bc1e89c04e13@posteo.net>
[-- Attachment #1: Type: text/plain, Size: 995 bytes --]
On Wed, Apr 08, 2026 at 05:59:27PM +0000, Stefan Bosch wrote:
> Hi Tom,
>
> On 07.04.26 19:26, Tom Rini wrote:
> > On Tue, Apr 07, 2026 at 05:23:19PM +0000, Stefan Bosch wrote:
> >
> > > s5p4418-pinctrl.dtsi: Fix mmc bus definitions to fix "mmc write failed"
> > > e.g. when cmd saveenv is executed. Initialize all four GPIO of the
> > > mmc-buses instead of only the first one.
> > >
> > > Signed-off-by: Stefan Bosch <stefan_b@posteo.net>
> > > ---
> > >
> > > arch/arm/dts/s5p4418-pinctrl.dtsi | 6 +++---
> > > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > Hey, I'm curious what it would take to move this to using OF_UPSTREAM,
> > where I assume this problem has already been fixed? Thanks!
> >
> If I'm not mistaken, using OF_UPSTREAM is not possible because I think the
> s5p4418 SoC is not in the Linux kernel source tree and therefore also not in
> the devicetree-rebasing repo.
Ah. That would be higher bar to clear. OK, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-04-08 18:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 17:23 [PATCH v1] arm: dts: s5p4418: fix "mmc write failed" e.g. at cmd saveenv Stefan Bosch
2026-04-07 17:26 ` Tom Rini
2026-04-08 17:59 ` Stefan Bosch
2026-04-08 18:05 ` Tom Rini [this message]
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=20260408180549.GL41863@bill-the-cat \
--to=trini@konsulko.com \
--cc=stefan_b@posteo.net \
--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