All of lore.kernel.org
 help / color / mirror / Atom feed
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2 v2] pinctrl: skip deferral of hogs
Date: Wed, 12 Dec 2012 15:26:08 -0700	[thread overview]
Message-ID: <50C90480.2010703@wwwdotorg.org> (raw)
In-Reply-To: <1355342027-2287-1-git-send-email-linus.walleij@stericsson.com>

On 12/12/2012 12:53 PM, Linus Walleij wrote:
> From: Linus Walleij <linus.walleij@linaro.org>
> 
> Up until now, as hogs were always taken at the end of the
> pin control device registration, it didn't cause any problem.
> But when starting to hog pins from the device core it will
> cause deferral of the pin controller device itself since the
> default pin fetch is done *before* the device probes, so
> let's fix this annoyance (which is also aesthetically ugly).
> 
> Also take some care to make sure that if any one map entry
> results in a deferral rather than a failure, then that
> deferral will take precedence.

Reviewed-by: Stephen Warren <swarren@nvidia.com>

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Linus Walleij <linus.walleij@stericsson.com>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Stephen Warren <swarren@nvidia.com>,
	Anmar Oueja <anmar.oueja@linaro.org>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 2/2 v2] pinctrl: skip deferral of hogs
Date: Wed, 12 Dec 2012 15:26:08 -0700	[thread overview]
Message-ID: <50C90480.2010703@wwwdotorg.org> (raw)
In-Reply-To: <1355342027-2287-1-git-send-email-linus.walleij@stericsson.com>

On 12/12/2012 12:53 PM, Linus Walleij wrote:
> From: Linus Walleij <linus.walleij@linaro.org>
> 
> Up until now, as hogs were always taken at the end of the
> pin control device registration, it didn't cause any problem.
> But when starting to hog pins from the device core it will
> cause deferral of the pin controller device itself since the
> default pin fetch is done *before* the device probes, so
> let's fix this annoyance (which is also aesthetically ugly).
> 
> Also take some care to make sure that if any one map entry
> results in a deferral rather than a failure, then that
> deferral will take precedence.

Reviewed-by: Stephen Warren <swarren@nvidia.com>

  reply	other threads:[~2012-12-12 22:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-12 19:53 [PATCH 2/2 v2] pinctrl: skip deferral of hogs Linus Walleij
2012-12-12 19:53 ` Linus Walleij
2012-12-12 22:26 ` Stephen Warren [this message]
2012-12-12 22:26   ` Stephen Warren

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=50C90480.2010703@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.