[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdZbpKqG_uS2N8TW2-HL5CqnuKDpHVCabf66MyQQof0jOw@mail.gmail.com>
Date: Sun, 5 Dec 2021 01:06:07 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Marc Zyngier <maz@...nel.org>,
Matti Vaittinen <matti.vaittinen@...rohmeurope.com>,
Sergio Paracuellos <sergio.paracuellos@...il.com>,
Chunyan Zhang <chunyan.zhang@...soc.com>,
Bartosz Golaszewski <brgl@...ev.pl>,
Baruch Siach <baruch@...s.co.il>,
Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>, Tony Lindgren <tony@...mide.com>,
Nicolas Saenz Julienne <nsaenz@...nel.org>,
Jianqun Xu <jay.xu@...k-chips.com>,
Alexandru Ardelean <aardelean@...iqon.com>,
Thierry Reding <treding@...dia.com>,
linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org,
patches@...nsource.cirrus.com,
bcm-kernel-feedback-list@...adcom.com,
linux-power@...rohmeurope.com,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, linux-pwm@...r.kernel.org,
linux-omap@...r.kernel.org, linux-unisoc@...ts.infradead.org,
linux-rockchip@...ts.infradead.org,
linux-stm32@...md-mailman.stormreply.com,
linux-tegra@...r.kernel.org, Ray Jui <rjui@...adcom.com>,
Florian Fainelli <f.fainelli@...il.com>,
Scott Branden <sbranden@...adcom.com>,
Gregory Fong <gregory.0xf0@...il.com>,
Eugeniy Paltsev <Eugeniy.Paltsev@...opsys.com>,
Keerthy <j-keerthy@...com>, Orson Zhai <orsonzhai@...il.com>,
Baolin Wang <baolin.wang7@...il.com>,
Chunyan Zhang <zhang.lyra@...il.com>,
Vladimir Zapolskiy <vz@...ia.com>,
Matthias Brugger <matthias.bgg@...il.com>,
Thierry Reding <thierry.reding@...il.com>,
Lee Jones <lee.jones@...aro.org>,
Grygorii Strashko <grygorii.strashko@...com>,
Santosh Shilimkar <ssantosh@...nel.org>,
Kevin Hilman <khilman@...nel.org>,
Robert Jarzmik <robert.jarzmik@...e.fr>,
Manivannan Sadhasivam <mani@...nel.org>,
Heiko Stuebner <heiko@...ech.de>,
Ludovic Desroches <ludovic.desroches@...rochip.com>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Alexandre Torgue <alexandre.torgue@...s.st.com>,
Jonathan Hunter <jonathanh@...dia.com>
Subject: Re: [PATCH v1 1/3] gpio: Get rid of duplicate of_node assignment in
the drivers
On Thu, Dec 2, 2021 at 10:17 PM Andy Shevchenko
<andriy.shevchenko@...ux.intel.com> wrote:
> GPIO library does copy the of_node from the parent device of
> the GPIO chip, there is no need to repeat this in the individual
> drivers. Remove these assignment all at once.
>
> For the details one may look into the of_gpio_dev_init() implementation.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
This is definitely a patch in the right direction, as Bart says
it can be a bit dangerous, the outliers are those drivers that
assign the .dev to something completely different than the
the dev where the of_node is copied from.
The idea was definitely always to only assign it in the core
*unless* there is a reason to have a completely different
of_node for some reason.
> +++ b/drivers/gpio/gpio-rda.c
> @@ -240,8 +240,6 @@ static int rda_gpio_probe(struct platform_device *pdev)
> rda_gpio->chip.label = dev_name(dev);
> rda_gpio->chip.ngpio = ngpios;
> rda_gpio->chip.base = -1;
> - rda_gpio->chip.parent = dev;
> - rda_gpio->chip.of_node = np;
Mention in the commit message that in this driver
you also drop the the .parent assignment because the
core will handle it.
Yours,
Linus Walleij
Powered by blists - more mailing lists