mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Olliver Schinagl <oliver@schinagl.nl>
To: Olliver Schinagl <oliver+list@schinagl.nl>,
	Thierry Reding <thierry.reding@gmail.com>
Cc: linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pwm: core: cleanup pointer tests
Date: Fri, 07 Aug 2015 20:18:52 +0200	[thread overview]
Message-ID: <55C4F68C.9070200@schinagl.nl> (raw)
In-Reply-To: <1438958976-1821-1-git-send-email-oliver+list@schinagl.nl>

Hey list,

After working on a new pwm-driver I noticed that not everybody actually 
has the set_polarity op and thus its an optional property. For a moment 
I figured I could add a 'software' polarity function by inverting the 
calculation of the on/off time, but I don't even have the hardware to 
test it so ...

Sorry for the noise, this patch can be ignored.

Olliver

On 07-08-15 16:49, Olliver Schinagl wrote:
> From: Olliver Schinagl <oliver@schinagl.nl>
>
> pwm_set_polarity() checks if there's ops and polarity function pointers.
> Most of these pointers are actually checked when a chip is added via
> pwm_add, except for set_polarity.
>
> This patch adds set_polarity to the list of functions to test on
> pwmchip_add_with_polarity(); and removes these checks from
> pwm_set_polarity.
>
> The pwm should be valid, as it was checked during
> pwmchip_add_with_polarity().
>
> Signed-off-by: Olliver Schinagl <oliver@schinagl.nl>
> ---
>   drivers/pwm/core.c | 8 +++-----
>   1 file changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/pwm/core.c b/drivers/pwm/core.c
> index 3a7769f..66fd5fd 100644
> --- a/drivers/pwm/core.c
> +++ b/drivers/pwm/core.c
> @@ -239,7 +239,8 @@ int pwmchip_add_with_polarity(struct pwm_chip *chip,
>   	int ret;
>   
>   	if (!chip || !chip->dev || !chip->ops || !chip->ops->config ||
> -	    !chip->ops->enable || !chip->ops->disable || !chip->npwm)
> +	    !chip->ops->set_polarity || !chip->ops->enable ||
> +	    !chip->ops->disable || !chip->npwm)
>   		return -EINVAL;
>   
>   	mutex_lock(&pwm_lock);
> @@ -449,12 +450,9 @@ int pwm_set_polarity(struct pwm_device *pwm, enum pwm_polarity polarity)
>   {
>   	int err;
>   
> -	if (!pwm || !pwm->chip->ops)
> +	if (!pwm)
>   		return -EINVAL;
>   
> -	if (!pwm->chip->ops->set_polarity)
> -		return -ENOSYS;
> -
>   	if (test_bit(PWMF_ENABLED, &pwm->flags))
>   		return -EBUSY;
>   


      reply	other threads:[~2015-08-07 18:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07 14:49 Olliver Schinagl
2015-08-07 18:18 ` Olliver Schinagl [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=55C4F68C.9070200@schinagl.nl \
    --to=oliver@schinagl.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=oliver+list@schinagl.nl \
    --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

all inboxes | Powered by JetHome®