All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org, sashiko-reviews@lists.linux.dev
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	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] ARM: dts: renesas: r9a06g032-rzn1d400-eb: enable GPIOs on CN12
Date: Thu, 16 Jul 2026 10:24:54 +0200	[thread overview]
Message-ID: <aliVVqnokN4s856T@ninjato> (raw)
In-Reply-To: <alfNV-_Cb3WlqiHB@shikoro>

[-- Attachment #1: Type: text/plain, Size: 1383 bytes --]


> > The snps,dw-apb-gpio driver iterates over its port subnodes (like gpio2b)
> > to register gpio_chip interfaces, but it doesn't appear to register these
> > subnodes as independent platform devices.
> >
> > Because the driver core only applies pinctrl-0 properties automatically
> > during probe for fully initialized device instances, this configuration
> > might be silently ignored by the kernel.
>
> True. Will rework.

After some more research: not true

gpiolib handles this, check this comment:

5351 /*
5352  * The DT node of some GPIO chips have a "compatible" property, but
5353  * never have a struct device added and probed by a driver to register
5354  * the GPIO chip with gpiolib. In such cases, fw_devlink=on will cause
5355  * the consumers of the GPIO chip to get probe deferred forever because
5356  * they will be waiting for a device associated with the GPIO chip
5357  * firmware node to get added and bound to a driver.
5358  *
5359  * To allow these consumers to probe, we associate the struct
5360  * gpio_device of the GPIO chip with the firmware node and then simply
5361  * bind it to this stub driver.
5362  */

Further proof, 'pinmux-pins' in debugfs shows that these pins are tied
to the gpiochip with this patch. It doesn't without this patch.

I think it is okay as-is. But I need to make another update anyhow, so I
will send a v2 nonetheless.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2026-07-16  8:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-15 12:21 [PATCH] ARM: dts: renesas: r9a06g032-rzn1d400-eb: enable GPIOs on CN12 Wolfram Sang
2026-07-15 12:40 ` sashiko-bot
2026-07-15 18:11 ` Wolfram Sang
2026-07-16  8:24   ` Wolfram Sang [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=aliVVqnokN4s856T@ninjato \
    --to=wsa+renesas@sang-engineering.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=krzk+dt@kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.