From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: linux-pwm@vger.kernel.org
Cc: Peter Griffin <peter.griffin@linaro.org>,
Lee Jones <lee@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
kernel@pengutronix.de
Subject: Re: [PATCH] pwm: sti: Fix capture for st, pwm-num-chan < st, capture-num-chan
Date: Wed, 7 Feb 2024 22:02:52 +0100 [thread overview]
Message-ID: <ke2smhqbjkqwdvqgrad3t2zlmsk5fvdbqzdfo74fpsutpqxmn7@my3otofvpxze> (raw)
In-Reply-To: <20240204212043.2951852-2-u.kleine-koenig@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 936 bytes --]
Hello,
On Sun, Feb 04, 2024 at 10:20:43PM +0100, Uwe Kleine-König wrote:
> The driver only used the number of pwm channels to set the pwm_chip's
> npwm member. The result is that if there are more capture channels than
> PWM channels specified in the device tree, only a part of the capture
> channel is usable. Fix that by passing the bigger channel count to the
> pwm framework. This makes it possible that the .apply() callback is
> called with .hwpwm >= pwm_num_devs, catch that case and return an error
> code.
>
> Fixes: c97267ae831d ("pwm: sti: Add PWM capture callback")
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux.git pwm/for-next
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2024-02-07 21:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 21:20 [PATCH] pwm: sti: Fix capture for st,pwm-num-chan < st,capture-num-chan Uwe Kleine-König
2024-02-07 21:02 ` Uwe Kleine-König [this message]
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=ke2smhqbjkqwdvqgrad3t2zlmsk5fvdbqzdfo74fpsutpqxmn7@my3otofvpxze \
--to=u.kleine-koenig@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=lee@kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=thierry.reding@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).