[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ea1be8af-0948-46b1-a1f4-fe572861cde4@roeck-us.net>
Date: Thu, 24 Oct 2024 09:07:30 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Uwe Kleine-König <u.kleine-koenig@...libre.com>,
Billy Tsai <billy_tsai@...eedtech.com>
Cc: jdelvare@...e.com, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, joel@....id.au, andrew@...econstruct.com.au,
linux-hwmon@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-aspeed@...ts.ozlabs.org,
linux-kernel@...r.kernel.org, linux-pwm@...r.kernel.org,
BMC-SW@...eedtech.com
Subject: Re: [PATCH v1 0/2] Enable WDT reload feature
On 10/24/24 08:40, Uwe Kleine-König wrote:
> Hello,
>
> On Thu, Oct 24, 2024 at 03:15:46PM +0800, Billy Tsai wrote:
>> Aspeed PWM controller has the WDT reload feature, which changes the duty
>> cycle to a preprogrammed value after a WDT/EXTRST#.
>>
>> Billy Tsai (2):
>> hwmon: (aspeed-g6-pwm-tacho): Extend the #pwm-cells to 4
>> hwmon: (aspeed-g6-pwm-tacho): Support the WDT reload
>
> Huh, I'm not convinced that extending #pwm-cells for that feature is a
> good idea. Unless I'm missing something none of the other supported PWM
> chips can do that, so I hesitate to change a standard for it. I suggest
> to make this a separate property instead.
>
Agreed.
Guenter
Powered by blists - more mailing lists