From: Kory Maincent <kory.maincent@bootlin.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Oleksij Rempel <o.rempel@pengutronix.de>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
kernel@pengutronix.de,
Dent Project <dentproject@linuxfoundation.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
Kyle Swenson <kyle.swenson@est.tech>
Subject: Re: [PATCH net-next 2/2] net: pse-pd: pd692x0: Add sysfs interface for configuration save/reset
Date: Mon, 25 Aug 2025 10:47:21 +0200 [thread overview]
Message-ID: <20250825104721.28f127a2@kmaincent-XPS-13-7390> (raw)
In-Reply-To: <d4bc2c95-7e25-4d76-994f-b68f1ead8119@lunn.ch>
Hello Andrew,
Le Fri, 22 Aug 2025 19:17:55 +0200,
Andrew Lunn <andrew@lunn.ch> a écrit :
> On Fri, Aug 22, 2025 at 05:37:02PM +0200, Kory Maincent wrote:
> > From: Kory Maincent (Dent Project) <kory.maincent@bootlin.com>
> >
> > Add sysfs attributes save_conf and reset_conf to enable userspace
> > management of the PSE's permanent configuration stored in EEPROM.
> >
> > The save_conf attribute allows saving the current configuration to
> > EEPROM by writing '1'. The reset_conf attribute restores factory
> > defaults and reinitializes the port matrix configuration.
>
> I'm not sure sysfs is the correct interface for this.
>
> Lets take a step back.
>
> I assume ethtool will report the correct state after a reboot when the
> EEPROM has content? The driver does not hold configuration state which
> cannot be represented in the EEPROM?
In fact I assumed it is an EEPROM but it is described as non volatile memory
so I don't know which type it is.
Yes ethtool report the current configuration which match the saved one if it has
been saved before. No the driver doesn't hold any state that can not be
represented in the non-volatile memory.
> Is the EEPROM mandatory, or optional? Is it built into the controller?
It is built into the controller. It seem there are version of this
controller that does not support it : "This command is not supported by
PD69200M."
> How fast is it to store the settings?
2 i2c messages and a 50 ms wait as described in the datasheet.
> I'm wondering if rather than having this sysfs parameter, you just
> store every configuration change? That could be more intuitive.
I have not thought of it. I don't know if it is a good idea. We may need
feedback from people that actually use PSE on field. Kyle any idea on this?
In any case we still need a way to reset the configuration through sysfs or
whatever other way.
> I've not looked at the sysfs documentation. Are there other examples
> of such a property?
Not sure for that particular save/reset configuration case.
Have you another implementation idea in mind?
Regards,
--
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-08-25 8:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 15:37 [PATCH net-next 0/2] net: pse-pd: pd692x0: Add permanent configuration management support Kory Maincent
2025-08-22 15:37 ` [PATCH net-next 1/2] net: pse-pd: pd692x0: Separate configuration parsing from hardware setup Kory Maincent
2025-08-25 22:10 ` Jakub Kicinski
2025-08-28 8:46 ` Kory Maincent
2025-08-28 22:12 ` Jakub Kicinski
2025-08-29 8:26 ` Kory Maincent
2025-08-29 23:58 ` Jakub Kicinski
2025-08-22 15:37 ` [PATCH net-next 2/2] net: pse-pd: pd692x0: Add sysfs interface for configuration save/reset Kory Maincent
2025-08-22 17:17 ` Andrew Lunn
2025-08-25 8:47 ` Kory Maincent [this message]
2025-08-25 9:14 ` Oleksij Rempel
2025-08-25 12:18 ` Andrew Lunn
2025-08-25 22:14 ` Jakub Kicinski
2025-08-28 11:29 ` Kory Maincent
2025-08-28 22:15 ` Jakub Kicinski
2025-08-25 12:20 ` Kory Maincent
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=20250825104721.28f127a2@kmaincent-XPS-13-7390 \
--to=kory.maincent@bootlin.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dentproject@linuxfoundation.org \
--cc=edumazet@google.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=kyle.swenson@est.tech \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.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