netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kory Maincent <kory.maincent@bootlin.com>
To: Oleksij Rempel <o.rempel@pengutronix.de>,
	 "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	 Jakub Kicinski <kuba@kernel.org>,
	Paolo Abeni <pabeni@redhat.com>,  Andrew Lunn <andrew@lunn.ch>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	netdev@vger.kernel.org,  linux-kernel@vger.kernel.org,
	Kyle Swenson <kyle.swenson@est.tech>,
	 Kory Maincent <kory.maincent@bootlin.com>
Subject: [PATCH net-next v3 2/3] net: pse-pd: pse_core: Fix pse regulator type
Date: Tue, 23 Apr 2024 11:21:11 +0200	[thread overview]
Message-ID: <20240423-fix_poe-v3-2-e50f32f5fa59@bootlin.com> (raw)
In-Reply-To: <20240423-fix_poe-v3-0-e50f32f5fa59@bootlin.com>

From: Kory Maincent (Dent Project) <kory.maincent@bootlin.com>

Clarify PSE regulator as voltage regulator, not current.
The PSE (Power Sourcing Equipment) regulator is defined as a voltage
regulator, maintaining fixed voltage while accommodating varying current.

Fixes: d83e13761d5b ("net: pse-pd: Use regulator framework within PSE framework")
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Acked-by: Oleksij Rempel <o.rempel@pengutronix.de>
Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
---
Change in v3:
- Add a missing Fixes tag.
---
 drivers/net/pse-pd/pse_core.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/pse-pd/pse_core.c b/drivers/net/pse-pd/pse_core.c
index bad29eaa4d01..795ab264eaf2 100644
--- a/drivers/net/pse-pd/pse_core.c
+++ b/drivers/net/pse-pd/pse_core.c
@@ -294,7 +294,7 @@ devm_pse_pi_regulator_register(struct pse_controller_dev *pcdev,
 	 */
 	rdesc->id = id;
 	rdesc->name = name;
-	rdesc->type = REGULATOR_CURRENT;
+	rdesc->type = REGULATOR_VOLTAGE;
 	rdesc->ops = &pse_pi_ops;
 	rdesc->owner = pcdev->owner;
 

-- 
2.34.1


  parent reply	other threads:[~2024-04-23  9:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23  9:21 [PATCH net-next v3 0/3] net: pse-pd: Fixes for few small issues Kory Maincent
2024-04-23  9:21 ` [PATCH net-next v3 1/3] net: pse-pd: pse_core: Add missing kdoc return description Kory Maincent
2024-04-25  3:50   ` patchwork-bot+netdevbpf
2024-04-23  9:21 ` Kory Maincent [this message]
2024-04-23  9:21 ` [PATCH net-next v3 3/3] net: pse-pd: Kconfig: Add missing Regulator API dependency Kory Maincent
2024-04-23 11:28 ` [PATCH net-next v3 0/3] net: pse-pd: Fixes for few small issues Jiri Pirko
2024-04-25  8:31   ` Kory Maincent
2024-04-25 14:06     ` Jakub Kicinski
2024-04-25 14:30       ` Kory Maincent
2024-04-25 14:42         ` Jakub Kicinski
2024-04-25 14:54           ` Kory Maincent
2024-04-25 14:57           ` Kory Maincent
2024-04-25 15:07             ` Jakub Kicinski
2024-04-25 17:04               ` Kory Maincent
2024-04-25 17:15                 ` Jakub Kicinski
2024-04-26  7:29                   ` 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=20240423-fix_poe-v3-2-e50f32f5fa59@bootlin.com \
    --to=kory.maincent@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=kyle.swenson@est.tech \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).