All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: sashiko-reviews@lists.linux.dev
Cc: Ben Zong-You Xie via B4 Relay
	<devnull+ben717.andestech.com@kernel.org>,
	 conor+dt@kernel.org, robh@kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v6 2/3] pwm: add Andes PWM driver support
Date: Mon, 10 Aug 2026 06:50:24 +0200	[thread overview]
Message-ID: <anlXaad2BMush07G@monoceros> (raw)
In-Reply-To: <20260625104613.CFCD41F00A3A@smtp.kernel.org>

[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]

Hello,

On Thu, Jun 25, 2026 at 10:46:13AM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [High] The driver fails to update the hardware PARK level to the inactive state when disabling the PWM channel, leaving the output stuck ON or at the wrong polarity.

I didn't look in detail into the patch yet, but I think the review
feedback here is misleading. There is no promise about a hardware state
for a disabled channel. The only objective is to save power.

Having said that, it's *nice* to drive the inactive level, but if that
isn't easily possible (e.g. because the output goes to high-Z on
disable) the primary objective is to save power.

So I guess the feedback is OK, but not "High".

> Additionally, if the polarity changes while the channel is disabled, will the
> hardware's inactive level fail to update?

This is in the same category. It's a bit surprising, but well in the
limits of what a PWM consumer must expect.

Best regards
Uwe

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2026-08-10  4:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-25 10:35 [PATCH v6 0/3] pwm: add support for Andes platform Ben Zong-You Xie
2026-06-25 10:35 ` Ben Zong-You Xie via B4 Relay
2026-06-25 10:35 ` [PATCH v6 1/3] dt-bindings: pwm: add support for AE350 PWM controller Ben Zong-You Xie
2026-06-25 10:35   ` Ben Zong-You Xie via B4 Relay
2026-06-25 10:45   ` sashiko-bot
2026-06-25 10:36 ` [PATCH v6 2/3] pwm: add Andes PWM driver support Ben Zong-You Xie
2026-06-25 10:36   ` Ben Zong-You Xie via B4 Relay
2026-06-25 10:46   ` sashiko-bot
2026-08-10  4:50     ` Uwe Kleine-König [this message]
2026-08-10  8:19   ` Uwe Kleine-König
2026-08-11 10:11     ` Ben Zong-You Xie
2026-06-25 10:36 ` [PATCH v6 3/3] MAINTAINERS: add an entry for Andes PWM driver Ben Zong-You Xie
2026-06-25 10:36   ` Ben Zong-You Xie via B4 Relay

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=anlXaad2BMush07G@monoceros \
    --to=u.kleine-koenig@baylibre.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=devnull+ben717.andestech.com@kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.