From: Adam Ford <aford173@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Sean Anderson <sean.anderson@linux.dev>,
linux-arm-kernel@lists.infradead.org,
Marian-Cristian Rotariu
<marian-cristian.rotariu.rb@bp.renesas.com>,
Biju Das <biju.das@bp.renesas.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
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>,
Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 0/2] arm64: dts: renesas: Add SD/OE pin properties
Date: Fri, 27 Sep 2024 07:51:31 -0500 [thread overview]
Message-ID: <CAHCN7xK4WxuLCbR_C6v7QKgoRkzuGoXq92YVQQOTTajUgO7njw@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdW3Lnu+fLm6tsWvtysOGmvKJ-utNYGJRUpRXtRmOXpQiw@mail.gmail.com>
On Fri, Sep 27, 2024 at 7:38 AM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>
> Hi Adam,
>
> On Fri, Sep 27, 2024 at 2:20 PM Adam Ford <aford173@gmail.com> wrote:
> > On Thu, Sep 26, 2024 at 1:24 PM Sean Anderson <sean.anderson@linux.dev> wrote:
> > > > - Inspect (or send me) the schematic to determine the state of the SD/OE
> > > > pin during normal operation.
> >
> > The SD/OE pins on the Beacon boards are not tied high by default.
> > They have an optional pull-up resistor, but it is not populated by
> > default.
>
> Whoops, this "np" suffix is really tiny! I had completely missed it :-(
I have worked at Beacon/Logic PD for 10 years and I still miss the
'np' at times. It's done that way, so when the bill-of-material is
generated from the schematic, the system throws away anything with an
'np' suffix, but it makes it really easy to enable it and know what
the part should be.
adam
>
> 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
prev parent reply other threads:[~2024-09-27 12:51 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
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 [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=CAHCN7xK4WxuLCbR_C6v7QKgoRkzuGoXq92YVQQOTTajUgO7njw@mail.gmail.com \
--to=aford173@gmail.com \
--cc=arnd@arndb.de \
--cc=biju.das@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=krzk+dt@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--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=marian-cristian.rotariu.rb@bp.renesas.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).