mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Sonic Zhang <sonic.adi@gmail.com>, Axel Lin <axel.lin@ingics.com>,
	Grant Likely <grant.likely@linaro.org>,
	Steven Miao <realmz6@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	buildroot-devel@blackfin.uclinux.org,
	adi-buildroot-devel@lists.sourceforge.net,
	Sonic Zhang <sonic.zhang@analog.com>
Subject: Re: [PATCH] pinctrl: pinmux: Don't free pins requested by other devices
Date: Wed, 07 Aug 2013 11:09:13 -0600	[thread overview]
Message-ID: <52027F39.5050805@wwwdotorg.org> (raw)
In-Reply-To: <CACRpkdZMCO9Cw=SMk4cq8k0+eqYrK=kKsjfAHut1=PXjxS_6jA@mail.gmail.com>

On 08/07/2013 10:23 AM, Linus Walleij wrote:
> On Wed, Jul 17, 2013 at 7:31 AM, Sonic Zhang <sonic.adi@gmail.com> wrote:
> 
> I'd like Stephen and Axel to have a look at this as well...
> 
>> From: Sonic Zhang <sonic.zhang@analog.com>
>>
>> in pinmux_disable_setting after current device fails to request
>> the same pins.
>>
>> Signed-off-by: Sonic Zhang <sonic.zhang@analog.com>
> 
> I don't quite understand the patch. Can you provide more context?

Yes, the commit description needs to describe the problem this solves.

I'm *guessing* the issue is:

Something tries to enable a new mux setting on some pins. One of those
pins is already owned by something else. So, applying the current
setting fails. So, pinctrl core attempts to unapply the partially
applied setting. This ends up incorrectly over-writing the conflicting
ownership of the pins with NULL, and hence forgetting about it.

I think a better change would be something more along the lines of:

  for (i = 0; i < num_pins; i++)
+ 	if (this_device_owns_pin(pins[i])
  		pin_free(pctldev, pins[i], NULL);

?

Where this_device_owns_pin() might be someting like:

	desc->owning_setting == setting

(which would be a new field that needed to be assigned during
pinmux_enable_setting).

Or perhaps the strcmp() is fine.

>> diff --git a/drivers/pinctrl/pinmux.c b/drivers/pinctrl/pinmux.c
>> index 88cc509..9ebcf3b 100644
>> --- a/drivers/pinctrl/pinmux.c
>> +++ b/drivers/pinctrl/pinmux.c
>> @@ -482,13 +482,14 @@ void pinmux_disable_setting(struct pinctrl_setting const *setting)
>>                                  pins[i]);
>>                         continue;
>>                 }
>> +               /* And release the pins */
>> +               if (desc->mux_usecount &&
>> +                       !strcmp(desc->mux_owner, setting->dev_name))
>> +                       pin_free(pctldev, pins[i], NULL);
>> +
>>                 desc->mux_setting = NULL;
>>         }
>>
>> -       /* And release the pins */
>> -       for (i = 0; i < num_pins; i++)
>> -               pin_free(pctldev, pins[i], NULL);
>> -
> 
> For pinmux_disable_setting() to inspect desc->mux_usecount seems
> assymetric. This is something pin_free() should do, shouldn't it?
> 
> Should not this codepath be kept and a change made inside pin_free()
> for the check above instead?


  reply	other threads:[~2013-08-07 17:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-17  5:31 Sonic Zhang
2013-08-07 16:23 ` Linus Walleij
2013-08-07 17:09   ` Stephen Warren [this message]
2013-08-08  3:38     ` Sonic Zhang
2013-08-08  3:42   ` Sonic Zhang
2013-07-23  7:34 Sonic Zhang

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=52027F39.5050805@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=adi-buildroot-devel@lists.sourceforge.net \
    --cc=axel.lin@ingics.com \
    --cc=buildroot-devel@blackfin.uclinux.org \
    --cc=grant.likely@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=realmz6@gmail.com \
    --cc=sonic.adi@gmail.com \
    --cc=sonic.zhang@analog.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®