All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"goda (Renesas)" <yusuke.goda.sx@renesas.com>,
	"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [periperi] How to set default GPIO pin ?
Date: Sun, 28 Sep 2014 16:58:50 -0700 (PDT)	[thread overview]
Message-ID: <8738bb9u1a.wl%kuninori.morimoto.gx@gmail.com> (raw)
In-Reply-To: <2033766.6tR9OHe7ZC@avalon>


Hi Laurent, Linus

> > I have suggested adding GPIO hogs, so that a GPIO node can specify
> > that some GPIO's specified on the local ship be hogged high or
> > low at probe. Generic DT bindings and generic code in gpiolib.c.
> > 
> > gpios-hog-high = <....>;
> > gpios-hog-low = <....>;
> 
> How about just a gpios-hog property, with a list of gpio specifiers + flags ? 
> That's bikeshedding I suppose.
> 
> Morimoto-san, would you like to implement that ? :-)

Thank you for your help
OK, I try to implement this method (when I have time :)
Thank you

Best regards
---
Kuninori Morimoto

WARNING: multiple messages have this Message-ID (diff)
From: Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [periperi] How to set default GPIO pin ?
Date: Sun, 28 Sep 2014 23:58:50 +0000	[thread overview]
Message-ID: <8738bb9u1a.wl%kuninori.morimoto.gx@gmail.com> (raw)
In-Reply-To: <2033766.6tR9OHe7ZC@avalon>


Hi Laurent, Linus

> > I have suggested adding GPIO hogs, so that a GPIO node can specify
> > that some GPIO's specified on the local ship be hogged high or
> > low at probe. Generic DT bindings and generic code in gpiolib.c.
> > 
> > gpios-hog-high = <....>;
> > gpios-hog-low = <....>;
> 
> How about just a gpios-hog property, with a list of gpio specifiers + flags ? 
> That's bikeshedding I suppose.
> 
> Morimoto-san, would you like to implement that ? :-)

Thank you for your help
OK, I try to implement this method (when I have time :)
Thank you

Best regards
---
Kuninori Morimoto

WARNING: multiple messages have this Message-ID (diff)
From: kuninori.morimoto.gx@gmail.com (Kuninori Morimoto)
To: linux-arm-kernel@lists.infradead.org
Subject: [periperi] How to set default GPIO pin ?
Date: Sun, 28 Sep 2014 16:58:50 -0700 (PDT)	[thread overview]
Message-ID: <8738bb9u1a.wl%kuninori.morimoto.gx@gmail.com> (raw)
In-Reply-To: <2033766.6tR9OHe7ZC@avalon>


Hi Laurent, Linus

> > I have suggested adding GPIO hogs, so that a GPIO node can specify
> > that some GPIO's specified on the local ship be hogged high or
> > low at probe. Generic DT bindings and generic code in gpiolib.c.
> > 
> > gpios-hog-high = <....>;
> > gpios-hog-low = <....>;
> 
> How about just a gpios-hog property, with a list of gpio specifiers + flags ? 
> That's bikeshedding I suppose.
> 
> Morimoto-san, would you like to implement that ? :-)

Thank you for your help
OK, I try to implement this method (when I have time :)
Thank you

Best regards
---
Kuninori Morimoto

  reply	other threads:[~2014-09-28 23:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8738cc0vx9.wl%kuninori.morimoto.gx@gmail.com>
2014-09-10  8:55 ` [periperi] How to set default GPIO pin ? Laurent Pinchart
2014-09-10  8:55   ` Laurent Pinchart
2014-09-12  7:27   ` Kuninori Morimoto
2014-09-12  7:27     ` Kuninori Morimoto
2014-09-23 15:06   ` Linus Walleij
2014-09-23 15:06     ` Linus Walleij
2014-09-23 15:06     ` Linus Walleij
2014-09-28 21:25     ` Laurent Pinchart
2014-09-28 21:25       ` Laurent Pinchart
2014-09-28 21:25       ` Laurent Pinchart
2014-09-28 23:58       ` Kuninori Morimoto [this message]
2014-09-28 23:58         ` Kuninori Morimoto
2014-09-28 23:58         ` Kuninori Morimoto
2014-09-29  8:58       ` Linus Walleij
2014-09-29  8:58         ` Linus Walleij
2014-09-29  8:58         ` Linus Walleij

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=8738bb9u1a.wl%kuninori.morimoto.gx@gmail.com \
    --to=kuninori.morimoto.gx@gmail.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=yusuke.goda.sx@renesas.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 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.