From: Colin Foster <colin.foster@in-advantage.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "Linus Walleij" <linus.walleij@linaro.org>,
"Marc Zyngier" <maz@kernel.org>,
"Sam Shih" <sam.shih@mediatek.com>,
"Zhiyong Tao" <zhiyong.tao@mediatek.com>,
"Ludovic Desroches" <ludovic.desroches@microchip.com>,
"Claudiu Beznea" <claudiu.beznea@microchip.com>,
"Radim Pavlik" <radim.pavlik@tbs-biometrics.com>,
"Kavyasree Kotagiri" <kavyasree.kotagiri@microchip.com>,
"Douglas Anderson" <dianders@chromium.org>,
"Bjorn Andersson" <bjorn.andersson@linaro.org>,
"Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>,
"Herve Codina" <herve.codina@bootlin.com>,
linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-actions@lists.infradead.org, linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
alsa-devel@alsa-project.org, patches@opensource.cirrus.com,
linux-mediatek@lists.infradead.org, linux-oxnas@groups.io,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-msm@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
"Andreas Färber" <afaerber@suse.de>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Nicolas Saenz Julienne" <nsaenz@kernel.org>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Ray Jui" <rjui@broadcom.com>,
"Scott Branden" <sbranden@broadcom.com>,
"Charles Keepax" <ckeepax@opensource.cirrus.com>,
"Richard Fitzgerald" <rf@opensource.cirrus.com>,
"Sean Wang" <sean.wang@kernel.org>,
"Basavaraj Natikar" <Basavaraj.Natikar@amd.com>,
"Shyam Sundar S K" <Shyam-sundar.S-k@amd.com>,
"Nicolas Ferre" <nicolas.ferre@microchip.com>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
"Support Opensource" <support.opensource@diasemi.com>,
"Baruch Siach" <baruch@tkos.co.il>,
"Neil Armstrong" <narmstrong@baylibre.com>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
"Andy Gross" <agross@kernel.org>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Viresh Kumar" <vireshk@kernel.org>,
"Shiraz Hashim" <shiraz.linux.kernel@gmail.com>,
soc@kernel.org
Subject: Re: [PATCH v2 2/2] pinctrl: Propagate firmware node from a parent device
Date: Tue, 14 Dec 2021 08:38:18 -0800 [thread overview]
Message-ID: <20211214163818.GA2429@DESKTOP-LAINLKC.localdomain> (raw)
In-Reply-To: <20211214125855.33207-2-andriy.shevchenko@linux.intel.com>
On Tue, Dec 14, 2021 at 02:58:55PM +0200, Andy Shevchenko wrote:
> When creating MFD platform devices the firmware node is left unset.
> This, in particular, prevents GPIO library to use it for different
> purposes. Propagate firmware node from the parent device and let
> GPIO library do the right thing.
>
I came across the same thing this week. By populating the of_compatible
field of the mfd_cell, the child device will have the appropriate
firmware node populated. Unfortunately that currently means that I'll
have to put every device type in the MFD instead of in an of_match_table
in the child driver itself. Figuring that out is one of the next things
on my list.
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
next prev parent reply other threads:[~2021-12-14 16:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 12:58 [PATCH v2 1/2] pinctrl: Get rid of duplicate of_node assignment in the drivers Andy Shevchenko
2021-12-14 12:58 ` [PATCH v2 2/2] pinctrl: Propagate firmware node from a parent device Andy Shevchenko
2021-12-14 13:36 ` Andy Shevchenko
2021-12-14 16:38 ` Colin Foster [this message]
2021-12-16 3:19 ` [PATCH v2 1/2] pinctrl: Get rid of duplicate of_node assignment in the drivers 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=20211214163818.GA2429@DESKTOP-LAINLKC.localdomain \
--to=colin.foster@in-advantage.com \
--cc=Basavaraj.Natikar@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=afaerber@suse.de \
--cc=agross@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=alexandre.torgue@foss.st.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=baruch@tkos.co.il \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bjorn.andersson@linaro.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=claudiu.beznea@microchip.com \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=f.fainelli@gmail.com \
--cc=geert+renesas@glider.be \
--cc=herve.codina@bootlin.com \
--cc=kavyasree.kotagiri@microchip.com \
--cc=linus.walleij@linaro.org \
--cc=linux-actions@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-oxnas@groups.io \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=ludovic.desroches@microchip.com \
--cc=mani@kernel.org \
--cc=maz@kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=narmstrong@baylibre.com \
--cc=nicolas.ferre@microchip.com \
--cc=nsaenz@kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=radim.pavlik@tbs-biometrics.com \
--cc=rf@opensource.cirrus.com \
--cc=rjui@broadcom.com \
--cc=sam.shih@mediatek.com \
--cc=sbranden@broadcom.com \
--cc=sean.wang@kernel.org \
--cc=shiraz.linux.kernel@gmail.com \
--cc=soc@kernel.org \
--cc=support.opensource@diasemi.com \
--cc=vireshk@kernel.org \
--cc=zhiyong.tao@mediatek.com \
/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).