netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Luis Chamberlain <mcgrof@kernel.org>,
	Russ Weight <russ.weight@linux.dev>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Oleksij Rempel <o.rempel@pengutronix.de>,
	Mark Brown <broonie@kernel.org>,
	Frank Rowand <frowand.list@gmail.com>,
	Andrew Lunn <andrew@lunn.ch>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org, devicetree@vger.kernel.org,
	Dent Project <dentproject@linuxfoundation.org>
Subject: Re: [PATCH net-next v5 13/17] net: pse-pd: Use regulator framework within PSE framework
Date: Wed, 28 Feb 2024 12:48:01 +0000	[thread overview]
Message-ID: <20240228124801.GC292522@kernel.org> (raw)
In-Reply-To: <20240227-feature_poe-v5-13-28f0aa48246d@bootlin.com>

On Tue, Feb 27, 2024 at 03:42:55PM +0100, Kory Maincent wrote:

...

> diff --git a/include/linux/pse-pd/pse.h b/include/linux/pse-pd/pse.h
> index 522115cc6cef..a3e297cc2150 100644
> --- a/include/linux/pse-pd/pse.h
> +++ b/include/linux/pse-pd/pse.h
> @@ -55,10 +55,10 @@ struct pse_controller_ops {
>  	int (*ethtool_get_status)(struct pse_controller_dev *pcdev,
>  		unsigned long id, struct netlink_ext_ack *extack,
>  		struct pse_control_status *status);
> -	int (*ethtool_set_config)(struct pse_controller_dev *pcdev,
> -		unsigned long id, struct netlink_ext_ack *extack,
> -		const struct pse_control_config *config);
>  	int (*setup_pi_matrix)(struct pse_controller_dev *pcdev);
> +	int (*pi_is_enabled)(struct pse_controller_dev *pcdev, int id);
> +	int (*pi_enable)(struct pse_controller_dev *pcdev, int id);
> +	int (*pi_disable)(struct pse_controller_dev *pcdev, int id);

Hi Kory,

Please update the Kernel doc for struct pse_controller_ops to reflect the
added and removed fields.

>  };
>  
>  struct module;
> @@ -90,10 +90,14 @@ struct pse_pi_pairset {
>   *
>   * @pairset: table of the PSE PI pinout alternative for the two pairset
>   * @np: device node pointer of the PSE PI node
> + * @rdev: regulator represented by the PSE PI
> + * @enabled: PI enabled state
>   */
>  struct pse_pi {
>  	struct pse_pi_pairset pairset[2];
>  	struct device_node *np;
> +	struct regulator_dev *rdev;
> +	bool enabled;
>  };
>  
>  /**
> @@ -107,6 +111,8 @@ struct pse_pi {
>   * @of_pse_n_cells: number of cells in PSE line specifiers
>   * @nr_lines: number of PSE controls in this controller device
>   * @lock: Mutex for serialization access to the PSE controller
> + * @lock_owner: current owner of the mutex
> + * @ref_cnt: mutex's reference count

These newly documented fields don't seem to exist in struct
pse_controller_dev. Perhaps this is an left over from earlier development?

>   * @types: types of the PSE controller
>   * @pi: table of PSE PIs described in this controller device
>   * @of_legacy: flag set if the pse_pis devicetree node is not used
> @@ -132,7 +138,8 @@ struct device;
>  int devm_pse_controller_register(struct device *dev,
>  				 struct pse_controller_dev *pcdev);
>  
> -struct pse_control *of_pse_control_get(struct device_node *node);
> +struct pse_control *of_pse_control_get(struct device *dev,
> +				       struct device_node *node);
>  void pse_control_put(struct pse_control *psec);
>  
>  int pse_ethtool_get_status(struct pse_control *psec,
> @@ -147,7 +154,8 @@ bool pse_has_c33(struct pse_control *psec);
>  
>  #else
>  
> -static inline struct pse_control *of_pse_control_get(struct device_node *node)
> +static inline struct pse_control *of_pse_control_get(struct device *dev,
> +						     struct device_node *node)
>  {
>  	return ERR_PTR(-ENOENT);
>  }
> 
> -- 
> 2.25.1
> 
> 

  parent reply	other threads:[~2024-02-28 12:48 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-27 14:42 [PATCH net-next v5 00/17] net: Add support for Power over Ethernet (PoE) Kory Maincent
2024-02-27 14:42 ` [PATCH net-next v5 01/17] MAINTAINERS: net: Add Oleksij to pse-pd maintainers Kory Maincent
2024-02-27 14:42 ` [PATCH net-next v5 02/17] of: property: Add fw_devlink support for pse parent Kory Maincent
2024-02-27 14:42 ` [PATCH net-next v5 03/17] net: pse-pd: Rectify and adapt the naming of admin_cotrol member of struct pse_control_config Kory Maincent
2024-02-27 14:42 ` [PATCH net-next v5 04/17] ethtool: Expand Ethernet Power Equipment with c33 (PoE) alongside PoDL Kory Maincent
2024-02-27 14:42 ` [PATCH net-next v5 05/17] net: pse-pd: Introduce PSE types enumeration Kory Maincent
2024-02-27 14:42 ` [PATCH net-next v5 06/17] net: ethtool: pse-pd: Expand pse commands with the PSE PoE interface Kory Maincent
2024-02-27 14:42 ` [PATCH net-next v5 07/17] netlink: specs: Modify pse attribute prefix Kory Maincent
2024-02-27 14:42 ` [PATCH net-next v5 08/17] netlink: specs: Expand the pse netlink command with PoE interface Kory Maincent
2024-02-27 14:42 ` [PATCH net-next v5 09/17] MAINTAINERS: Add myself to pse networking maintainer Kory Maincent
2024-02-27 14:42 ` [PATCH net-next v5 10/17] net: pse-pd: Add support for PSE PIs Kory Maincent
2024-03-01 14:24   ` Oleksij Rempel
2024-03-01 16:10     ` Köry Maincent
2024-03-01 16:48       ` Oleksij Rempel
2024-02-27 14:42 ` [PATCH net-next v5 11/17] dt-bindings: net: pse-pd: Add another way of describing several " Kory Maincent
2024-02-28 16:42   ` Rob Herring
2024-02-27 14:42 ` [PATCH net-next v5 12/17] net: pse-pd: Add support for setup_pi_matrix callback Kory Maincent
2024-02-27 14:42 ` [PATCH net-next v5 13/17] net: pse-pd: Use regulator framework within PSE framework Kory Maincent
2024-02-28  0:56   ` Jakub Kicinski
2024-02-29 10:19     ` Köry Maincent
2024-02-28 12:48   ` Simon Horman [this message]
2024-02-29  9:41     ` Köry Maincent
2024-03-02 21:35   ` Oleksij Rempel
2024-03-04  9:27     ` Köry Maincent
2024-03-04 10:31       ` Oleksij Rempel
2024-03-21 16:15         ` Kory Maincent
2024-03-21 16:43           ` Oleksij Rempel
2024-03-22 10:39             ` Kory Maincent
2024-03-22 14:07               ` Oleksij Rempel
2024-03-22 14:22                 ` Kory Maincent
2024-03-04 13:32       ` Andrew Lunn
2024-03-04 13:39         ` Oleksij Rempel
2024-03-04 13:53           ` Andrew Lunn
2024-03-04 14:23             ` Oleksij Rempel
2024-02-27 14:42 ` [PATCH net-next v5 14/17] dt-bindings: net: pse-pd: Add bindings for PD692x0 PSE controller Kory Maincent
2024-02-27 14:42 ` [PATCH net-next v5 15/17] net: pse-pd: Add PD692x0 PSE controller driver Kory Maincent
2024-02-27 14:42 ` [PATCH net-next v5 16/17] dt-bindings: net: pse-pd: Add bindings for TPS23881 PSE controller Kory Maincent
2024-02-27 14:42 ` [PATCH net-next v5 17/17] net: pse-pd: Add TI TPS23881 PSE controller driver Kory Maincent
2024-02-28 12:53   ` Simon Horman
2024-02-29 11:09     ` Köry Maincent
2024-02-27 15:31 ` [PATCH net-next v5 00/17] net: Add support for Power over Ethernet (PoE) Jamal Hadi Salim
2024-03-08 13:54   ` Köry 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=20240228124801.GC292522@kernel.org \
    --to=horms@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=dentproject@linuxfoundation.org \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=frowand.list@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hkallweit1@gmail.com \
    --cc=kory.maincent@bootlin.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mcgrof@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=pabeni@redhat.com \
    --cc=rafael@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=russ.weight@linux.dev \
    --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).