From: Linus Walleij <linus.walleij@linaro.org> To: Johan Hovold <johan@kernel.org> Cc: "Markus Pargmann" <mpa@pengutronix.de>, "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>, "Alexandre Courbot" <gnurou@gmail.com>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, "Sascha Hauer" <kernel@pengutronix.de>, "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org> Subject: Re: [PATCH 3/9] gpio: Allow hogged gpios to be requested Date: Mon, 10 Aug 2015 11:20:00 +0200 [thread overview] Message-ID: <CACRpkdbHwCNttDCEUyYq_5REh1PDuR__XDeLD0mR6NqfO6h_HA@mail.gmail.com> (raw) In-Reply-To: <20150728091753.GJ28535@localhost> On Tue, Jul 28, 2015 at 11:17 AM, Johan Hovold <johan@kernel.org> wrote: > On Sun, Jul 19, 2015 at 04:01:42PM +0200, Markus Pargmann wrote: >> > I don't like this patch. IMHO hogging is a "use" of a GPIO that should >> > prevent it being requested. >> >> I disagree with you here. The original patch stated in its description >> that it was designed to initialize GPIOs. In my understanding this does >> not necessarily mean that a hogged GPIO has to be blocked forever. > > IIRC, this use case was discussed but was rejected by Linus when hogs > were added: > > https://lkml.kernel.org/r/CACRpkdZcNcPBYQM438CZJx1gYst9BFBSTj-3Qv2aPGF9pdWa5g@mail.gmail.com > > Linus? Yeah that is true. But maybe I softened up a bit. Basically I want to avoid having two very similar mechanisms. But that is maybe more of a question of how the code is arranged and named than what it is called. It would be nicer if this was referring to initial values rather than hogging, the mechanism inside the kernel could be the same. But then there is the path where something that is initially a hog is turned into a userspace GPIO. Then it is essentially not a hog anymore, so this property is not static. Yours, Linus Walleij
WARNING: multiple messages have this Message-ID (diff)
From: linus.walleij@linaro.org (Linus Walleij) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 3/9] gpio: Allow hogged gpios to be requested Date: Mon, 10 Aug 2015 11:20:00 +0200 [thread overview] Message-ID: <CACRpkdbHwCNttDCEUyYq_5REh1PDuR__XDeLD0mR6NqfO6h_HA@mail.gmail.com> (raw) In-Reply-To: <20150728091753.GJ28535@localhost> On Tue, Jul 28, 2015 at 11:17 AM, Johan Hovold <johan@kernel.org> wrote: > On Sun, Jul 19, 2015 at 04:01:42PM +0200, Markus Pargmann wrote: >> > I don't like this patch. IMHO hogging is a "use" of a GPIO that should >> > prevent it being requested. >> >> I disagree with you here. The original patch stated in its description >> that it was designed to initialize GPIOs. In my understanding this does >> not necessarily mean that a hogged GPIO has to be blocked forever. > > IIRC, this use case was discussed but was rejected by Linus when hogs > were added: > > https://lkml.kernel.org/r/CACRpkdZcNcPBYQM438CZJx1gYst9BFBSTj-3Qv2aPGF9pdWa5g at mail.gmail.com > > Linus? Yeah that is true. But maybe I softened up a bit. Basically I want to avoid having two very similar mechanisms. But that is maybe more of a question of how the code is arranged and named than what it is called. It would be nicer if this was referring to initial values rather than hogging, the mechanism inside the kernel could be the same. But then there is the path where something that is initially a hog is turned into a userspace GPIO. Then it is essentially not a hog anymore, so this property is not static. Yours, Linus Walleij
next prev parent reply other threads:[~2015-08-10 9:20 UTC|newest] Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-07-17 9:32 [PATCH 0/9] gpiolib: Add GPIO name support Markus Pargmann 2015-07-17 9:32 ` Markus Pargmann 2015-07-17 9:32 ` [PATCH 1/9] gpiolib: Fix possible use of wrong name Markus Pargmann 2015-07-17 9:32 ` Markus Pargmann 2015-07-28 9:03 ` Johan Hovold 2015-07-28 9:03 ` Johan Hovold 2015-07-29 6:46 ` Markus Pargmann 2015-07-29 6:46 ` Markus Pargmann 2015-07-17 9:32 ` [PATCH 2/9] gpiolib-of: Rename gpio_hog functions to be generic Markus Pargmann 2015-07-17 9:32 ` Markus Pargmann 2015-07-17 9:32 ` [PATCH 3/9] gpio: Allow hogged gpios to be requested Markus Pargmann 2015-07-17 9:32 ` Markus Pargmann 2015-07-17 20:27 ` Uwe Kleine-König 2015-07-17 20:27 ` Uwe Kleine-König 2015-07-19 14:01 ` Markus Pargmann 2015-07-19 14:01 ` Markus Pargmann 2015-07-20 6:32 ` Uwe Kleine-König 2015-07-20 6:32 ` Uwe Kleine-König 2015-07-20 7:51 ` Markus Pargmann 2015-07-20 7:51 ` Markus Pargmann 2015-07-28 9:17 ` Johan Hovold 2015-07-28 9:17 ` Johan Hovold 2015-07-29 6:52 ` Markus Pargmann 2015-07-29 6:52 ` Markus Pargmann 2015-08-10 9:20 ` Linus Walleij [this message] 2015-08-10 9:20 ` Linus Walleij 2015-07-17 9:32 ` [PATCH 4/9] gpio: Add 'name' to the gpio descriptor struct Markus Pargmann 2015-07-17 9:32 ` Markus Pargmann 2015-07-28 9:24 ` Johan Hovold 2015-07-28 9:24 ` Johan Hovold 2015-07-17 9:32 ` [PATCH 5/9] gpiolib: Implement gpio_name_to_desc() Markus Pargmann 2015-07-17 9:32 ` Markus Pargmann 2015-07-17 9:32 ` [PATCH 6/9] gpiolib-of: Reuse 'line-name' from DT as gpio descriptor name Markus Pargmann 2015-07-17 9:32 ` Markus Pargmann 2015-07-28 9:31 ` Johan Hovold 2015-07-28 9:31 ` Johan Hovold 2015-07-29 6:52 ` Markus Pargmann 2015-07-29 6:52 ` Markus Pargmann 2015-07-17 9:32 ` [PATCH 7/9] gpiolib-sysfs: Add gpio name parsing for sysfs export Markus Pargmann 2015-07-17 9:32 ` Markus Pargmann 2015-07-28 9:50 ` Johan Hovold 2015-07-28 9:50 ` Johan Hovold 2015-07-29 6:57 ` Markus Pargmann 2015-07-29 6:57 ` Markus Pargmann 2015-07-31 8:44 ` Johan Hovold 2015-07-31 8:44 ` Johan Hovold 2015-07-17 9:32 ` [PATCH 8/9] gpiolib-sysfs: Show gpio-name in /sys/class/gpio/gpio*/name Markus Pargmann 2015-07-17 9:32 ` Markus Pargmann 2015-07-28 9:53 ` Johan Hovold 2015-07-28 9:53 ` Johan Hovold 2015-07-29 7:02 ` Markus Pargmann 2015-07-29 7:02 ` Markus Pargmann 2015-07-17 9:32 ` [PATCH 9/9] gpiolib: Add gpio name information to /sys/kernel/debug/gpio Markus Pargmann 2015-07-17 9:32 ` Markus Pargmann 2015-07-28 9:58 ` Johan Hovold 2015-07-28 9:58 ` Johan Hovold 2015-07-29 7:08 ` Markus Pargmann 2015-07-29 7:08 ` Markus Pargmann 2015-07-31 8:54 ` Johan Hovold 2015-07-31 8:54 ` Johan Hovold 2015-07-31 10:41 ` Markus Pargmann 2015-07-31 10:41 ` Markus Pargmann 2015-07-31 10:45 ` Johan Hovold 2015-07-31 10:45 ` Johan Hovold 2015-07-31 10:49 ` Lucas Stach 2015-07-31 10:49 ` Lucas Stach 2015-07-17 20:05 ` [PATCH 0/9] gpiolib: Add GPIO name support Linus Walleij 2015-07-17 20:05 ` Linus Walleij 2015-07-21 9:00 ` Alexandre Courbot 2015-07-21 9:00 ` Alexandre Courbot 2015-07-21 9:54 ` Uwe Kleine-König 2015-07-21 9:54 ` Uwe Kleine-König 2015-07-21 10:10 ` Markus Pargmann 2015-07-21 10:10 ` Markus Pargmann [not found] ` <CAGmoSHt0Kg-cxe3U6uV40=ttmFbDruRcJZNxtmSZ=gmZQN5fTw@mail.gmail.com> 2015-07-31 9:49 ` Johan Hovold 2015-07-31 9:49 ` Johan Hovold 2015-07-31 10:42 ` Markus Pargmann 2015-07-31 10:42 ` Markus Pargmann 2015-07-28 14:16 ` Johan Hovold 2015-07-28 14:16 ` Johan Hovold 2015-07-29 9:23 ` Linus Walleij 2015-07-29 9:23 ` Linus Walleij 2015-07-31 9:40 ` Johan Hovold 2015-07-31 9:40 ` Johan Hovold
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=CACRpkdbHwCNttDCEUyYq_5REh1PDuR__XDeLD0mR6NqfO6h_HA@mail.gmail.com \ --to=linus.walleij@linaro.org \ --cc=gnurou@gmail.com \ --cc=johan@kernel.org \ --cc=kernel@pengutronix.de \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-gpio@vger.kernel.org \ --cc=mpa@pengutronix.de \ --cc=u.kleine-koenig@pengutronix.de \ /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: linkBe 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.