mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "eric miao" <eric.y.miao@gmail.com>
To: "David Brownell" <david-b@pacbell.net>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
	"Rtp Arnaud Patard" <arnaud.patard@rtp-net.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch 2.6.25-rc4] gpio/pca953x bugfix: mark as can_sleep
Date: Mon, 10 Mar 2008 13:14:35 +0800	[thread overview]
Message-ID: <f17812d70803092214x2fefe245i741902bc62dee9d2@mail.gmail.com> (raw)
In-Reply-To: <200803091356.20024.david-b@pacbell.net>

OK

On Mon, Mar 10, 2008 at 4:56 AM, David Brownell <david-b@pacbell.net> wrote:
> The pca953x driver is an I2C driver so gpio_chip->can_sleep should be set.
>  This lets upper layers know they should use the gpio_*_cansleep() calls
>  to access values, and may not access them from nonsleeping contexts.
>
>  Signed-off-by: Arnaud Patard <arnaud.patard@rtp-net.org>
>  Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
>  ---
>  Merge before 2.6.25-final, please.  This will for example prevent
>  leds-gpio from issuing blocking I2C calls from timer/irq contexts.
>
>   drivers/gpio/pca953x.c |    1 +
>   1 file changed, 1 insertion(+)
>
>  --- g26.orig/drivers/gpio/pca953x.c     2008-03-08 11:17:22.000000000 -0800
>  +++ g26/drivers/gpio/pca953x.c  2008-03-09 13:51:13.000000000 -0700
>  @@ -184,6 +184,7 @@ static void pca953x_setup_gpio(struct pc
>         gc->direction_output = pca953x_gpio_direction_output;
>         gc->get = pca953x_gpio_get_value;
>         gc->set = pca953x_gpio_set_value;
>  +       gc->can_sleep = 1;
>
>         gc->base = chip->gpio_start;
>         gc->ngpio = gpios;
>



-- 
Cheers
- eric

      reply	other threads:[~2008-03-10  5:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-09 20:56 David Brownell
2008-03-10  5:14 ` eric miao [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=f17812d70803092214x2fefe245i741902bc62dee9d2@mail.gmail.com \
    --to=eric.y.miao@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnaud.patard@rtp-net.org \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®