mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Manush Prajwal" <manushprajwal555@gmail.com>
To: ukleinek@kernel.org
Cc: linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pwm: tiehrpwm: fix copy-paste error in obsolete DT binding fallback
Date: 29 Sep 2026 15:36:40 +0530	[thread overview]
Message-ID: <6abb8db0.721b4d7a.30484d.cb00@mx.google.com> (raw)

Hi Uwe,

Thanks for the quick review and for digging up the Fixes commit.

> Looks right, I guess it needs:
> Fixes: ae5200d22716 ("pwm: pwm-ti*: Get the clock from the PWMSS parent when using old bindings")
> 
> I wonder: Did you find this because you still use the old bindings, or
> by code inspection somehow? If the latter, maybe it's time to drop the
> handling instead?

This was found purely by code inspection during a review of the PWM
drivers, not from running older bindings on actual hardware.

Given that this fallback in pwm-tiehrpwm has been effectively broken ever
since commit ae5200d22716 was merged in 2014 without anyone noticing or
reporting it, it seems very likely that nobody relies on this obsolete
binding anymore.

I would be happy to send a patch dropping the obsolete binding handling
instead (from pwm-tiehrpwm, or from both pwm-tiehrpwm and pwm-tiecap if
you prefer keeping them consistent).

Or if you'd rather keep backward compatibility, I can send a v2 of this
fix with the Fixes: tag included.

Which direction would you prefer?

Best regards,
Manush


             reply	other threads:[~2026-09-29 10:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29 10:06 Manush Prajwal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-09-28 17:55 Manush Prajwal
2026-09-29  6:00 ` Uwe Kleine-König

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=6abb8db0.721b4d7a.30484d.cb00@mx.google.com \
    --to=manushprajwal555@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=ukleinek@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

all inboxes | Powered by JetHome®