From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-renesas-soc@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/2] ARM: dts: renesas: r9a06g032-rzn1d400-eb: enable GPIOs on CN12
Date: Tue, 11 Aug 2026 03:51:38 +0200 [thread overview]
Message-ID: <anqAKtaFCxADeLqM@shikoro> (raw)
In-Reply-To: <CAMuHMdWCWvfFqBAQ40E+czhYHSG_ZuCqMobku6B2iEA8ezF5Cg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
> > + pins_gpio2b: pins-gpio2b {
>
> pins-cn12?
Okay.
> > + pinmux = <RZN1_PINMUX(164, RZN1_FUNC_GPIO)>,
> > + <RZN1_PINMUX(165, RZN1_FUNC_GPIO)>,
> > + <RZN1_PINMUX(166, RZN1_FUNC_GPIO)>,
> > + <RZN1_PINMUX(167, RZN1_FUNC_GPIO)>,
> > + <RZN1_PINMUX(168, RZN1_FUNC_GPIO)>,
> > + <RZN1_PINMUX(169, RZN1_FUNC_GPIO)>;
> > + drive-strength = <6>;
> > + bias-disable;
>
> These pins don't have any external pull-ups, so disabling bias will
> make them pick-up random EM noise when left unconnected.
Can fix, but is this bad? I'd assume the connected pins will handle it.
And if not, the DT needs to be adapted to that use case. Otherwise, a
default pull-up needs to be disabled for another use case.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-08-11 1:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 9:59 [PATCH v2 0/2] ARM: dts: renesas: r9a06g032-rzn1d400: GPIO updates Wolfram Sang
2026-07-16 9:59 ` [PATCH v2 1/2] ARM: dts: renesas: r9a06g032-rzn1d400: don't enable gpiochips which are always on Wolfram Sang
2026-08-10 13:16 ` Geert Uytterhoeven
2026-07-16 9:59 ` [PATCH v2 2/2] ARM: dts: renesas: r9a06g032-rzn1d400-eb: enable GPIOs on CN12 Wolfram Sang
2026-07-16 10:13 ` sashiko-bot
2026-07-16 10:20 ` Wolfram Sang
2026-08-10 13:27 ` Geert Uytterhoeven
2026-08-11 1:51 ` Wolfram Sang [this message]
2026-08-11 7:23 ` Geert Uytterhoeven
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=anqAKtaFCxADeLqM@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=krzk+dt@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh@kernel.org \
/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