Devicetree
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: Francesco Dolcini <francesco@dolcini.it>,
	Jean Delvare <jdelvare@suse.com>,
	Guenter Roeck <linux@roeck-us.net>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Farouk Bouabid <farouk.bouabid@cherry.de>
Cc: Francesco Dolcini <francesco.dolcini@toradex.com>,
	linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/2] hwmon: (amc6821) Add PWM polarity configuration with OF
Date: Wed, 19 Feb 2025 11:08:43 +0100	[thread overview]
Message-ID: <eb5c844a-e726-44c0-a0c1-7796d1a28ec3@cherry.de> (raw)
In-Reply-To: <20250218165633.106867-3-francesco@dolcini.it>

Hi Francesco,

On 2/18/25 5:56 PM, Francesco Dolcini wrote:
> From: Francesco Dolcini <francesco.dolcini@toradex.com>
> 
> Add support to configure the PWM-Out pin polarity based on a device
> tree property.
> 
> Signed-off-by: Francesco Dolcini <francesco.dolcini@toradex.com>
> ---
>   drivers/hwmon/amc6821.c | 7 +++++--
>   1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/hwmon/amc6821.c b/drivers/hwmon/amc6821.c
> index 1e3c6acd8974..1ea2d97eebca 100644
> --- a/drivers/hwmon/amc6821.c
> +++ b/drivers/hwmon/amc6821.c
> @@ -845,7 +845,7 @@ static int amc6821_detect(struct i2c_client *client, struct i2c_board_info *info
>   	return 0;
>   }
>   
> -static int amc6821_init_client(struct amc6821_data *data)
> +static int amc6821_init_client(struct i2c_client *client, struct amc6821_data *data)
>   {
>   	struct regmap *regmap = data->regmap;
>   	int err;
> @@ -864,6 +864,9 @@ static int amc6821_init_client(struct amc6821_data *data)
>   		if (err)
>   			return err;
>   
> +		if (of_property_read_bool(client->dev.of_node, "ti,pwm-inverted"))

I know that the AMC6821 is doing a lot of smart things, but this really 
tickled me. PWM controllers actually do support that already via 
PWM_POLARITY_INVERTED flag for example. See 
Documentation/devicetree/bindings/hwmon/adt7475.yaml which seems to be 
another HWMON driver which acts as a PWM controller. I'm not sure this 
is relevant, applicable or desired but I wanted to highlight this.

> +			pwminv = 1;
> +

This is silently overriding the module parameter.

I don't think this is a good idea, at the very least not silently.

I would suggest to add some logic in the probe function to set this 
value and check its consistency.

Something like:

"""
diff --git a/drivers/hwmon/amc6821.c b/drivers/hwmon/amc6821.c
index 1e3c6acd89740..3a13a914e2bbb 100644
--- a/drivers/hwmon/amc6821.c
+++ b/drivers/hwmon/amc6821.c
@@ -37,7 +37,7 @@ static const unsigned short normal_i2c[] = {0x18, 
0x19, 0x1a, 0x2c, 0x2d, 0x2e,
   * Insmod parameters
   */

-static int pwminv;	/*Inverted PWM output. */
+static int pwminv = -1;	/* -1 not modified by the user, 0 default PWM 
output, 1 inverted PWM output */
  module_param(pwminv, int, 0444);

  static int init = 1; /*Power-on initialization.*/
@@ -904,6 +904,7 @@ static int amc6821_probe(struct i2c_client *client)
  	struct amc6821_data *data;
  	struct device *hwmon_dev;
  	struct regmap *regmap;
+	bool pwminv_dt;
  	int err;

  	data = devm_kzalloc(dev, sizeof(struct amc6821_data), GFP_KERNEL);
@@ -916,6 +917,18 @@ static int amc6821_probe(struct i2c_client *client)
  				     "Failed to initialize regmap\n");
  	data->regmap = regmap;

+	pwminv_dt = of_property_read_bool(client->dev.of_node, "ti,pwm-inverted");
+
+	if (pwminv == -1) {
+		pwminv = pwminv_dt;
+	} else if (is_of_node(client->dev.fwnode)) {
+		if ((!pwminv_dt && pwminv) || (pwminv_dt && pwminv == 0)) {
+			dev_err(dev,
+				"Polarity of PWM output passed by module parameter (pwminv=%d) 
differs from the one provided through the Device Tree, ignoring Device 
Tree value\n",
+				pwminv);
+		}
+	}
+
  	err = amc6821_init_client(data);
  	if (err)
  		return err;
"""

maybe? Note that I have neither compiled nor tested this code.

This also changes the precedence compared to the patch you sent, I think 
we may want the module param to override the DT property if there's a 
conflict.

What do you think?

Cheers,
Quentin

  reply	other threads:[~2025-02-19 10:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18 16:56 [PATCH v1 0/2] hwmon: (amc6821) Add PWM polarity configuration with OF Francesco Dolcini
2025-02-18 16:56 ` [PATCH v1 1/2] dt-bindings: hwmon: amc6821: add PWM polarity Francesco Dolcini
2025-02-18 16:56 ` [PATCH v1 2/2] hwmon: (amc6821) Add PWM polarity configuration with OF Francesco Dolcini
2025-02-19 10:08   ` Quentin Schulz [this message]
2025-02-19 10:33     ` Francesco Dolcini
2025-02-19 11:12       ` Quentin Schulz
2025-02-19 16:20         ` Francesco Dolcini
2025-02-19 13:46     ` Guenter Roeck
2025-02-19 16:16       ` Francesco Dolcini

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=eb5c844a-e726-44c0-a0c1-7796d1a28ec3@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=farouk.bouabid@cherry.de \
    --cc=francesco.dolcini@toradex.com \
    --cc=francesco@dolcini.it \
    --cc=jdelvare@suse.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=robh@kernel.org \
    /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