From: Herve Codina <herve.codina@bootlin.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "Geert Uytterhoeven" <geert@linux-m68k.org>,
"Simon Horman" <horms@kernel.org>, "Lee Jones" <lee@kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Derek Kiernan" <derek.kiernan@amd.com>,
"Dragan Cvetic" <dragan.cvetic@amd.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Lars Povlsen" <lars.povlsen@microchip.com>,
"Steen Hegelund" <Steen.Hegelund@microchip.com>,
"Daniel Machon" <daniel.machon@microchip.com>,
UNGLinuxDriver@microchip.com, "Rob Herring" <robh@kernel.org>,
"Saravana Kannan" <saravanak@google.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Horatiu Vultur" <horatiu.vultur@microchip.com>,
"Andrew Lunn" <andrew@lunn.ch>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org,
"Allan Nielsen" <allan.nielsen@microchip.com>,
"Luca Ceresoli" <luca.ceresoli@bootlin.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Clément Léger" <clement.leger@bootlin.com>
Subject: Re: [PATCH v4 3/8] mfd: syscon: Add reference counting and device managed support
Date: Wed, 7 Aug 2024 15:29:27 +0200 [thread overview]
Message-ID: <20240807152927.22e40284@bootlin.com> (raw)
In-Reply-To: <CAHp75VfKXEyHF25xRq8EDp5SeBdyPHLgzw=4s1xkjer=sNu7aw@mail.gmail.com>
Hi Andy,
On Mon, 5 Aug 2024 22:20:56 +0200
Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> On Mon, Aug 5, 2024 at 12:19 PM Herve Codina <herve.codina@bootlin.com> wrote:
> >
> > From: Clément Léger <clement.leger@bootlin.com>
> >
> > Syscon releasing is not supported.
> > Without release function, unbinding a driver that uses syscon whether
> > explicitly or due to a module removal left the used syscon in a in-use
> > state.
> >
> > For instance a syscon_node_to_regmap() call from a consumer retrieve a
>
> retrieves?
Indeed, will be fixed.
>
> > syscon regmap instance. Internally, syscon_node_to_regmap() can create
> > syscon instance and add it to the existing syscon list. No API is
> > available to release this syscon instance, remove it from the list and
> > free it when it is not used anymore.
> >
> > Introduce reference counting in syscon in order to keep track of syscon
> > usage using syscon_{get,put}() and add a device managed version of
> > syscon_regmap_lookup_by_phandle(), to automatically release the syscon
> > instance on the consumer removal.
>
> ...
>
> > - if (!syscon)
> > + if (!syscon) {
> > syscon = of_syscon_register(np, check_res);
> > + if (IS_ERR(syscon))
> > + return ERR_CAST(syscon);
> > + } else {
> > + syscon_get(syscon);
> > + }
>
> if (syscon)
> return syscon_get();
>
> ?
>
> > + return syscon;
Yes and further more, I will remove also the unneeded IS_ERR() and ERR_CAST().
This will lead to just:
if (syscon)
return syscon_get(syscon);
return of_syscon_register(np, check_res);
>
> ...
>
> > +static struct regmap *__devm_syscon_get(struct device *dev,
> > + struct syscon *syscon)
> > +{
> > + struct syscon **ptr;
> > +
> > + if (IS_ERR(syscon))
> > + return ERR_CAST(syscon);
> > +
> > + ptr = devres_alloc(devm_syscon_release, sizeof(struct syscon *), GFP_KERNEL);
> > + if (!ptr) {
> > + syscon_put(syscon);
> > + return ERR_PTR(-ENOMEM);
> > + }
> > +
> > + *ptr = syscon;
> > + devres_add(dev, ptr);
> > +
> > + return syscon->regmap;
>
> Can't the devm_add_action_or_reset() be used in this case? If so,
> perhaps a comment to explain why?
There is no reason to avoid the use of devm_add_action_or_reset() here.
So, I will use it in the next iteration.
Thanks for your review.
Best regards,
Hervé
next prev parent reply other threads:[~2024-08-07 13:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 10:17 [PATCH v4 0/8] Add support for the LAN966x PCI device using a DT overlay Herve Codina
2024-08-05 10:17 ` [PATCH v4 1/8] misc: Add support for LAN966x PCI device Herve Codina
2024-08-05 20:13 ` Andy Shevchenko
2024-08-07 10:09 ` Herve Codina
2024-08-08 12:32 ` Andy Shevchenko
2024-08-08 14:07 ` Herve Codina
2024-08-05 10:17 ` [PATCH v4 2/8] MAINTAINERS: Add the Microchip LAN966x PCI driver entry Herve Codina
2024-08-05 10:17 ` [PATCH v4 3/8] mfd: syscon: Add reference counting and device managed support Herve Codina
2024-08-05 20:20 ` Andy Shevchenko
2024-08-07 13:29 ` Herve Codina [this message]
2024-08-05 10:17 ` [PATCH v4 4/8] reset: mchp: sparx5: Add MCHP_LAN966X_PCI dependency Herve Codina
2024-08-07 7:57 ` Steen Hegelund
2024-08-05 10:17 ` [PATCH v4 5/8] reset: mchp: sparx5: Allow building as a module Herve Codina
2024-08-07 9:14 ` Steen Hegelund
2024-08-05 10:17 ` [PATCH v4 6/8] reset: mchp: sparx5: Release syscon when not use anymore Herve Codina
2024-08-07 9:48 ` Steen Hegelund
2024-08-05 10:17 ` [PATCH v4 7/8] reset: core: add get_device()/put_device on rcdev Herve Codina
2024-08-05 10:17 ` [PATCH v4 8/8] reset: mchp: sparx5: set the dev member of the reset controller Herve Codina
2024-08-08 8:22 ` Steen Hegelund
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=20240807152927.22e40284@bootlin.com \
--to=herve.codina@bootlin.com \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=allan.nielsen@microchip.com \
--cc=andrew@lunn.ch \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=clement.leger@bootlin.com \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=derek.kiernan@amd.com \
--cc=devicetree@vger.kernel.org \
--cc=dragan.cvetic@amd.com \
--cc=edumazet@google.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=horatiu.vultur@microchip.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=lars.povlsen@microchip.com \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=saravanak@google.com \
--cc=thomas.petazzoni@bootlin.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 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.