From: Alexander Holler <holler@ahsoftware.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"davinci-linux-open-source@linux.davincidsp.com"
<davinci-linux-open-source@linux.davincidsp.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Alexandre Courbot <gnurou@gmail.com>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Sekhar Nori <nsekhar@ti.com>,
Prabhakar Lad <prabhakar.csengg@gmail.com>
Subject: Re: [PATCH v2] gpio: davinci: fix gpio selection for OF
Date: Fri, 14 Mar 2014 13:38:02 +0100 [thread overview]
Message-ID: <5322F82A.9000507@ahsoftware.de> (raw)
In-Reply-To: <CACRpkdaghneo1MvNCfxjTED+sJepHgeZCgmKsRteG9qrBNWAfQ@mail.gmail.com>
Am 14.03.2014 12:02, schrieb Linus Walleij:
> On Fri, Mar 14, 2014 at 11:08 AM, Alexander Holler <holler@ahsoftware.de> wrote:
>> Am 11.03.2014 11:15, schrieb Linus Walleij:
>>> On Wed, Mar 5, 2014 at 12:21 PM, Alexander Holler <holler@ahsoftware.de> wrote:
>>>
>>>> The driver missed an of_xlate function to translate gpio numbers
>>>> as found in the DT to the correct chip and number.
>>>>
>>>> While there I've set #gpio_cells to a fixed value of 2.
>>>>
>>>> I've used gpio-pxa.c as template for those changes and tested my changes
>>>> successfully on a da850 board using entries for gpio-leds in a DT. So I didn't
>>>> reinvent the wheel but just copied and tested stuff.
>>>>
>>>> Thanks to Grygorii Strashko for the hint to the existing code in gpio-pxa.
>>>>
>>>> Signed-off-by: Alexander Holler <holler@ahsoftware.de>
>>>> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
>>>
>>> This v2 version applied, thanks!
>>
>> Thanks, but actually that should have been a fix for 3.14 with which the
>> OF functionality for davinci gpio gets introduced. I assum with the
>> patch in for-next, 3.14 will appear with that functionality broken and
>> it will become a candidate for -stable.
>
> I just get the impression that DT support for DaVinci in v3.14 is so risky
> and unstable that noone except those implementing it (i.e. you) is really
> using it, is that correct?
Yes. DT support for DaVinci is still incomplete and I don't think there
are much people out there which already try to use it. Nevertheless is
using DT a much easier way (and more future-proof) than patching
board-files, if a board isn't one of those few supported dev-boards and
needs different configurations.
> In that case it is hardly a fix that we need to rush out to the entire world.
Hmm, I think it's better to send something working and tested to world,
than something untested and non-working.
And especially things like pinctrl and gpio are fundamental to even try
to use DT. E.g. in my case I didn't even try to use DT for DaVinci
because it doesn't make sense without support for DT in gpio. And now
people will get promised but broken support for gpio in 3.14, which
might cost a lot of time, if someone tries to use it.
And I thought the reason for -rc is actually to fix bugs. But I never
understood the magical ways and timings patches make their way into
mainline. ;)
Regards,
Alexander Holler
next prev parent reply other threads:[~2014-03-14 12:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5315ED51.1000006@ti.com>
[not found] ` <5315ED51.1000006-l0cyMroinI0@public.gmane.org>
2014-03-04 22:06 ` [PATCH] gpio: davinci: fix gpio selection for OF Alexander Holler
[not found] ` <1393970762-5346-1-git-send-email-holler-SXC+2es9fhnfWeYVQQPykw@public.gmane.org>
2014-03-05 2:27 ` Linus Walleij
2014-03-05 10:43 ` Grygorii Strashko
[not found] ` <5316FFCE.1060603-l0cyMroinI0@public.gmane.org>
2014-03-05 11:21 ` [PATCH v2] " Alexander Holler
[not found] ` <1394018461-757-1-git-send-email-holler-SXC+2es9fhnfWeYVQQPykw@public.gmane.org>
2014-03-05 13:12 ` Grygorii Strashko
2014-03-11 10:15 ` Linus Walleij
[not found] ` <CACRpkdaF=jc9Z1XZCtH8VPuih01t--qyV-sgH1R_ix0VM4RzVA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-14 10:08 ` Alexander Holler
2014-03-14 11:02 ` Linus Walleij
2014-03-14 12:38 ` Alexander Holler [this message]
2014-03-14 13:54 ` Linus Walleij
2014-03-14 18:33 ` Alexander Holler
2014-03-14 19:52 ` Linus Walleij
2014-03-15 7:37 ` Alexander Holler
2014-03-17 13:29 ` Sekhar Nori
2014-03-17 14:05 ` Linus Walleij
[not found] ` <CACRpkdYZMzw31NkA4uSq+ZowzOnZgZthXhZri-eJY2Ozb8aNRQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-18 8:37 ` Sekhar Nori
[not found] ` <532805AE.9000806-l0cyMroinI0@public.gmane.org>
2014-03-18 9:45 ` Alexander Holler
[not found] ` <532815A8.9090807-SXC+2es9fhnfWeYVQQPykw@public.gmane.org>
2014-03-18 10:54 ` Sekhar Nori
2014-03-21 8:28 ` Linus Walleij
2014-03-21 8:59 ` Alexander Holler
[not found] ` <5326F8C5.5090406-l0cyMroinI0@public.gmane.org>
2014-03-17 14:11 ` Alexander Holler
2014-03-17 14:13 ` Linus Walleij
2014-03-17 15:04 ` Grygorii Strashko
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=5322F82A.9000507@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=grant.likely@linaro.org \
--cc=grygorii.strashko@ti.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=prabhakar.csengg@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).