From: Thierry Reding <thierry.reding@gmail.com>
To: Axel Lin <axel.lin@ingics.com>
Cc: Brian Norris <computersforpeace@gmail.com>,
Gregory Fong <gregory.0xf0@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
linux-pwm@vger.kernel.org
Subject: Re: [PATCH RESEND] pwm: brcmstb: Don't set can_sleep flag
Date: Tue, 24 Nov 2015 17:27:10 +0100 [thread overview]
Message-ID: <20151124162710.GD32623@ulmo.nvidia.com> (raw)
In-Reply-To: <1448347392.17722.1.camel@ingics.com>
[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]
On Tue, Nov 24, 2015 at 02:43:12PM +0800, Axel Lin wrote:
> The .can_sleep flag is used for some PWM controllers that can't be used
> in atomic context. Not such case for this driver, so don't set the
> can_sleep flag.
>
> Signed-off-by: Axel Lin <axel.lin@ingics.com>
> Acked-by: Florian Fainelli <f.fainelli@gmail.com>
> Reviewed-by: Brian Norris <computersforpeace@gmail.com>
> ---
> This patch was sent on http://www.spinics.net/lists/linux-pwm/msg03506.html
>
> drivers/pwm/pwm-brcmstb.c | 1 -
> 1 file changed, 1 deletion(-)
There's some discussion currently about marking all drivers can_sleep
and modify all users to cope with it correctly. The reason is that we
introduced a mutex in pwm_enable() and pwm_set_polarity() which means
that PWM devices effectively can't be used from interrupt or atomic
contexts.
It also means that the driver is actually currently correct, so I'd
like to leave it as-is until the users have been sorted out, at which
point we can simply get rid of can_sleep.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-11-24 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 6:43 [PATCH RESEND] pwm: brcmstb: Don't set can_sleep flag Axel Lin
2015-11-24 16:27 ` Thierry Reding [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=20151124162710.GD32623@ulmo.nvidia.com \
--to=thierry.reding@gmail.com \
--cc=axel.lin@ingics.com \
--cc=computersforpeace@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=gregory.0xf0@gmail.com \
--cc=linux-pwm@vger.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;
as well as URLs for NNTP newsgroup(s).