On Wed, Nov 27, 2024 at 11:11:26AM +0100, Kory Maincent wrote: > On Wed, 27 Nov 2024 10:30:43 +0100 > Oleksij Rempel <o.rempel@xxxxxxxxxxxxxx> wrote: > > > On Tue, Nov 26, 2024 at 04:52:28PM +0100, Kory Maincent wrote: > > > On Tue, 26 Nov 2024 16:31:55 +0100 > > > Kory Maincent <kory.maincent@xxxxxxxxxxx> wrote: > > > > > > > Hello Oleksij, > > > > > > > > Thanks for your quick reviews! > > > > > > > > On Tue, 26 Nov 2024 09:38:27 +0100 > > > > Oleksij Rempel <o.rempel@xxxxxxxxxxxxxx> wrote: > > > > > > [...] > > [...] > > > > > > We already talked about it but a policies per port seems irrelevant to me. > > > https://lore.kernel.org/netdev/ZySR75i3BEzNbjnv@xxxxxxxxxxxxxx/ > > > How do we compare the priority value of ports that use different budget > > > strategy? How do we manage in the same power domain two ports with > > > different budget strategies or disconnection policies? > > > > Good question :) > > > > > We indeed may need a separate interface to configure the PSE power domain > > > budget strategies and disconnection policies. > > > > And a way to upload everything in atomic way, but I see it as > > optimization and can be done separately > > > > > I think not being able to set the budget evaluation strategy is not relevant > > > for now as we don't have PSE which could support both, > > > > Both can be implemented for TI. By constantly polling the channel > > current register, it should be possible to implement dynamic strategy. > > > > > but being able to set the disconnection policies may be relevant. > > > If we don't add this support to this series how do we decide which is the > > > default disconnection policy supported? > > > > Use hard coded one ¯\_(ツ)_/¯ > > I think we could start with disabled disconnection policy for now. > The user cans still play with the priority value which is really reasonable as > there is as many priority values as PSE ports in the static strategy. Hm, since prios without disconnecting do not make sens and it looks more like all disconnection policies are optimizations steps for configurations with multiple ports having same prio, i would suggest an implementation where no same prios are allowed on multiple ports. > Should we still report it in the status as there is no disconnection policy? > Maybe we could add it at the time we will support several disconnection > policies. Yes. It would be better to have a discussion with some one having real use case. -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
