From: claudiu beznea <claudiu.beznea@tuxon.dev>
To: Manikandan Muralidharan <manikandan.m@microchip.com>,
linus.walleij@linaro.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, nicolas.ferre@microchip.com,
alexandre.belloni@bootlin.com, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/4] ARM: dts: microchip: change to simple-mfd from simple-bus for PIO3 pinumux controller
Date: Sat, 24 Aug 2024 17:32:19 +0300 [thread overview]
Message-ID: <b6307e8c-1ef0-483e-9091-83949166743c@tuxon.dev> (raw)
In-Reply-To: <20240814061315.112564-2-manikandan.m@microchip.com>
On 14.08.2024 09:13, Manikandan Muralidharan wrote:
> The pinctrl subnodes that define the pin configuration of other devices
> under PIO3 pinmux controller are not simple memory mapped nodes.Ergo,
> change simple-bus to simple-mfd.
>
> Signed-off-by: Manikandan Muralidharan <manikandan.m@microchip.com>
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
Applied to at91-dt, thanks!
next prev parent reply other threads:[~2024-08-24 14:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 6:13 [PATCH v4 0/4] Convert Atmel PIO3 Pinctrl and GPIO bindings to yaml Manikandan Muralidharan
2024-08-14 6:13 ` [PATCH v4 1/4] ARM: dts: microchip: change to simple-mfd from simple-bus for PIO3 pinumux controller Manikandan Muralidharan
2024-08-24 14:32 ` claudiu beznea [this message]
2024-08-14 6:13 ` [PATCH v4 2/4] ARM: dts: microchip: Remove additional compatible string from PIO3 pinctrl nodes Manikandan Muralidharan
2024-08-24 14:32 ` claudiu beznea
2025-04-16 14:04 ` Ahmad Fatoum
2025-04-17 7:48 ` Linus Walleij
2024-08-14 6:13 ` [PATCH v4 3/4] ARM: dts: microchip: sam9x60: Remove additional compatible string from GPIO node Manikandan Muralidharan
2024-08-24 14:33 ` claudiu beznea
2024-08-14 6:13 ` [PATCH v4 4/4] dt-bindings: pinctrl: Convert Atmel PIO3 pinctrl to json-schema Manikandan Muralidharan
2024-08-24 14:35 ` claudiu beznea
2024-08-30 11:55 ` Linus Walleij
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=b6307e8c-1ef0-483e-9091-83949166743c@tuxon.dev \
--to=claudiu.beznea@tuxon.dev \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manikandan.m@microchip.com \
--cc=nicolas.ferre@microchip.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;
as well as URLs for NNTP newsgroup(s).