From: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
To: Oleksij Rempel <ore@pengutronix.de>, Rob Herring <robh+dt@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Alexandre Courbot <gnurou@gmail.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Oleksij Rempel <o.rempel@pengutronix.de>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
barebox@lists.infradead.org
Subject: Re: [PATCH v1 1/1] gpio: of: provide option generic property for initial line states
Date: Sun, 11 Jun 2017 22:57:18 +0300 [thread overview]
Message-ID: <2432df7e-5d20-42c9-ddc0-044c2ca5ce2b@mentor.com> (raw)
In-Reply-To: <20170611061919.jsbc7x67ut4segj5@pengutronix.de>
Hi Oleksij,
On 06/11/2017 09:19 AM, Oleksij Rempel wrote:
> Hi Rob,
>
> On Fri, Jun 09, 2017 at 10:41:30AM -0500, Rob Herring wrote:
>> On Fri, Jun 9, 2017 at 9:16 AM, Oleksij Rempel <o.rempel@pengutronix.de> wrote:
>>> This property is needed for barebox or may be other bootloaders
>>> to set proper gpio configuration as early as possible.
>>>
>>> This example is mainly based on "lines-initial-states" property
>>> from this binding documentation:
>>> Documentation/devicetree/bindings/gpio/gpio-pcf857x.txt
>>
>> Don't we have a binding for this already based on gpio-hogs.
>
> Markus Pargmann was working on this topic before and suddenly was not
> able to finish it.
that's fine, but the proposed extension is supposedly not wanted.
> I found only some not finished discussions and no code or documentation
> in linux kernel upstream.
>
> So far, I was able to find fallowing patches and discussions:
> patch 23.08.2015, last comment 11.05.2017:
> https://patchwork.kernel.org/patch/7096721/
>
> patch 23.02.2016, last comment 09.03.2016:
> https://patchwork.ozlabs.org/patch/586743/
>
> Since there was objections about node-like design for gpio-initval, I
> provided an array property, which is similar to initval properties already used
> for different other device nodes. For example:
>
> Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt
> qcom,ath10k-calibration-data
>
> Documentation/devicetree/bindings/gpio/gpio-pcf857x.txt
> lines-initial-states
It'd rather be better to fix the drivers and remove the properties
from these found device tree binding descriptions.
>
> Please fixme if I miss something.
Why is GPIO hogging mechanism not good enough for your purpose?
--
With best wishes,
Vladimir
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2017-06-11 19:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 14:16 Oleksij Rempel
2017-06-09 15:41 ` Rob Herring
2017-06-11 6:19 ` Oleksij Rempel
2017-06-11 19:57 ` Vladimir Zapolskiy [this message]
2017-06-15 5:56 ` Oleksij Rempel
2017-06-15 9:48 ` Vladimir Zapolskiy
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=2432df7e-5d20-42c9-ddc0-044c2ca5ce2b@mentor.com \
--to=vladimir_zapolskiy@mentor.com \
--cc=barebox@lists.infradead.org \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=o.rempel@pengutronix.de \
--cc=ore@pengutronix.de \
--cc=robh+dt@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