From: Herve Codina <herve.codina@bootlin.com>
To: Lee Jones <lee@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Steen Hegelund <Steen.Hegelund@microchip.com>
Cc: "Geert Uytterhoeven" <geert@linux-m68k.org>,
"Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Simon Horman" <horms@kernel.org>,
"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>,
"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 v5 3/8] mfd: syscon: Add reference counting and device managed support
Date: Mon, 23 Sep 2024 10:07:41 +0200 [thread overview]
Message-ID: <20240923100741.11277439@bootlin.com> (raw)
In-Reply-To: <20240912143740.GD24460@google.com>
Hi,
On Thu, 12 Sep 2024 15:37:40 +0100
Lee Jones <lee@kernel.org> wrote:
> On Mon, 09 Sep 2024, Herve Codina wrote:
>
> > Hi Lee, Arnd,
> >
> > On Tue, 3 Sep 2024 18:01:16 +0200
> > Herve Codina <herve.codina@bootlin.com> wrote:
> >
> > > Hi Lee,
> > >
> > > On Tue, 3 Sep 2024 16:38:39 +0100
> > > Lee Jones <lee@kernel.org> wrote:
> > >
> > > > On Thu, 08 Aug 2024, Herve Codina 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 retrieves a
> > > > > 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.
> > > > >
> > > > > Signed-off-by: Clément Léger <clement.leger@bootlin.com>
> > > > > Signed-off-by: Herve Codina <herve.codina@bootlin.com>
> > > > > ---
> > > > > drivers/mfd/syscon.c | 138 ++++++++++++++++++++++++++++++++++---
> > > > > include/linux/mfd/syscon.h | 16 +++++
> > > > > 2 files changed, 144 insertions(+), 10 deletions(-)
> > > >
> > > > This doesn't look very popular.
> > > >
> > > > What are the potential ramifications for existing users?
> > > >
> > >
> > > Existing user don't use devm_syscon_regmap_lookup_by_phandle() nor
> > > syscon_put_regmap().
> > >
> > > So refcount is incremented but never decremented. syscon is never
> > > released. Exactly the same as current implementation.
> > > Nothing change for existing users.
> > >
> > > Best regards,
> > > Hervé
> >
> > I hope I answered to Lee's question related to possible impacts on
> > existing drivers.
> >
> > Is there anything else that blocks this patch from being applied ?
>
> Arnd usually takes care of Syscon reviews.
>
> Perhaps he's out on vacation.
>
> Let's wait a little longer, since it's too late for this cycle anyway.
>
Discussed the topic with Arnd Bergmann at Linux Plumbers Conference.
Adding ref-counting and support for removal in syscon is rejected by Arnd.
For my LAN966x use case (syscon is used only by the reset controller), the
solution is to remove the syscon device and handle directly the reset protect
register in the reset controller itself.
I will propose modifications in that way in the next iteration.
Regards,
Hervé
next prev parent reply other threads:[~2024-09-23 8:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 15:46 [PATCH v5 0/8] Add support for the LAN966x PCI device using a DT overlay Herve Codina
2024-08-08 15:46 ` [PATCH v5 1/8] misc: Add support for LAN966x PCI device Herve Codina
2024-08-13 9:57 ` Greg Kroah-Hartman
2024-09-09 7:45 ` Herve Codina
2024-09-12 17:00 ` Bjorn Helgaas
2024-08-08 15:46 ` [PATCH v5 2/8] MAINTAINERS: Add the Microchip LAN966x PCI driver entry Herve Codina
2024-08-08 15:46 ` [PATCH v5 3/8] mfd: syscon: Add reference counting and device managed support Herve Codina
2024-09-03 15:38 ` Lee Jones
2024-09-03 16:01 ` Herve Codina
2024-09-09 7:52 ` Herve Codina
2024-09-12 14:37 ` Lee Jones
2024-09-23 8:07 ` Herve Codina [this message]
2024-08-08 15:46 ` [PATCH v5 4/8] reset: mchp: sparx5: Add MCHP_LAN966X_PCI dependency Herve Codina
2024-08-08 15:46 ` [PATCH v5 5/8] reset: mchp: sparx5: Allow building as a module Herve Codina
2024-08-08 15:46 ` [PATCH v5 6/8] reset: mchp: sparx5: Release syscon when not use anymore Herve Codina
2024-08-08 15:46 ` [PATCH v5 7/8] reset: core: add get_device()/put_device on rcdev Herve Codina
2024-09-02 10:01 ` Philipp Zabel
2024-08-08 15:46 ` [PATCH v5 8/8] reset: mchp: sparx5: set the dev member of the reset controller Herve Codina
2024-09-02 10:49 ` [PATCH v5 0/8] Add support for the LAN966x PCI device using a DT overlay Philipp Zabel
2024-09-03 8:17 ` Herve Codina
2024-09-03 9:51 ` Lee Jones
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=20240923100741.11277439@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 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).