devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Sean Anderson <sean.anderson@linux.dev>
Cc: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
	linux-arm-kernel@lists.infradead.org,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Rob Herring <robh@kernel.org>,
	linux-renesas-soc@vger.kernel.org,  linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org,  Conor Dooley <conor+dt@kernel.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	 Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH 1/2] arm64: dts: renesas: salvator-xs: Add SD/OE pin properties
Date: Mon, 7 Oct 2024 14:12:57 +0200	[thread overview]
Message-ID: <CAMuHMdVCfb5AJcAMRTzDThPz5DzmduFwROob-Y2QO6P47Ry4HQ@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdUz2boLeoaynsHHM_26XqNFCJhTLYx9+zEHCG+ZMRwKVg@mail.gmail.com>

On Fri, Sep 27, 2024 at 12:34 PM Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
> On Thu, Sep 26, 2024 at 8:09 PM Sean Anderson <sean.anderson@linux.dev> wrote:
> > Add SD/OE pin properties to the devicetree so that Linux can configure
> > the pin without relying on the OTP. This matches the register
> > configuration reported by Geert [1], as well as my inspection of the
> > schematic (which shows the SD/OE pin permanently tied high).
> >
> > [1] https://lore.kernel.org/linux-clk/CAMuHMdW9LMuQLuPEF-Fcs1E6Q7dDzY17VZqu4awKDj5WSTRt=A@mail.gmail.com/
> >
> > Signed-off-by: Sean Anderson <sean.anderson@linux.dev>
>
> Thanks for your patch!
>
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
> There is no change in the output of
>
>     grep 10: /sys/kernel/debug/regmap/*-006a/registers
>
> before/after this patch, so
> Tested-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
> BTW, I applied the same patch to salvator-x.dtsi, and that seems to be
> fine, too.

Thanks, will queue in renesas-devel for v6.13.

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2024-10-07 12:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-26 18:09 [PATCH 0/2] arm64: dts: renesas: Add SD/OE pin properties Sean Anderson
2024-09-26 18:09 ` [PATCH 1/2] arm64: dts: renesas: salvator-xs: " Sean Anderson
2024-09-27 10:34   ` Geert Uytterhoeven
2024-10-07 12:12     ` Geert Uytterhoeven [this message]
2024-09-26 18:09 ` [PATCH 2/2] arm64: dts: renesas: ulcb: " Sean Anderson
2024-09-27 10:34   ` Geert Uytterhoeven
2024-10-07 12:14     ` Geert Uytterhoeven
2024-09-26 18:24 ` [PATCH 0/2] arm64: dts: renesas: " Sean Anderson
2024-09-27 10:07   ` Geert Uytterhoeven
2024-09-27 12:19   ` Adam Ford
2024-09-27 12:38     ` Geert Uytterhoeven
2024-09-27 12:51       ` Adam Ford

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=CAMuHMdVCfb5AJcAMRTzDThPz5DzmduFwROob-Y2QO6P47Ry4HQ@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=arnd@arndb.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=olof@lixom.net \
    --cc=robh@kernel.org \
    --cc=sean.anderson@linux.dev \
    /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;
as well as URLs for NNTP newsgroup(s).