From: Linus Walleij <linus.walleij@linaro.org>
To: Christian Lamparter <chunkeey@gmail.com>,
Laxman Dewangan <ldewangan@nvidia.com>,
Stephen Warren <swarren@wwwdotorg.org>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
linux-arm-msm@vger.kernel.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
David Brown <david.brown@linaro.org>,
Sven Eckelmann <sven.eckelmann@openmesh.com>,
Andy Gross <andy.gross@linaro.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] pinctrl: msm: fix gpio-hog related boot issues
Date: Wed, 2 May 2018 14:14:39 +0200 [thread overview]
Message-ID: <CACRpkdaEYFerKQa4QRCFEg2TOrdbnF6SfVZ9chLpmCxSUNcZBw@mail.gmail.com> (raw)
In-Reply-To: <3524410.JrO1DEFpQ1@debian64>
On Thu, Apr 26, 2018 at 11:47 PM, Christian Lamparter
<chunkeey@gmail.com> wrote:
> On Thu, Apr 26, 2018 11:12:21 CEST Linus Walleij wrote:
>> I think I replied in some other mail that I think we need to
>> be backwards compatible and it's not too hard to do
>> both. (Correct me if I'm wrong.)
>
> I think so too, I looked around and found that the nvidia pinctrl was
> doing something similar with of_find_property():
> <https://elixir.bootlin.com/linux/v4.17-rc2/source/drivers/pinctrl/tegra/pinctrl-tegra.c#L652>
> | has_prop = of_find_property(np, "gpio-ranges", NULL);
>
> However this looks kinda funny, since "has_prob" is declared as a bool
> and of_find_property() returns a pointer to a "struct property"....
> Tell you what: If nobody beats me to it, I'll sent a patch for this after
> the pinctrl-msm's gpio-hog has been dealt with. :)
Yeah the nVidia driver is one of the oldest and also at the time
DT was kind of new. I haven't heard from Stephen for a while
but I bet he will pop up, else check with Laxman, he's got
a good grip on nVidia pinctrl+GPIO as well.
> And as you can probably guess: The License is sold as a yearly subscription
> starting from $150 for a single device. So, these devices became practically
> e-waste since nobody in their right mind would buy a used device and then
> fork over the ~$150 fee per annum.
>
> The MR24 craze is mostly over by now. You can still find a few. However
> some listings are now selling them with OpenWrt/LEDE for ~$40.
>
> And obviously, this cycle will continue on, but now with the old wave1
> 802.11ac gear that gets replaced. In fact this business has spawned
> companies that are actively working on supporting "old" enterprise gear
> via their own OpenWrt/LEDE derivatives.
Haha that is just awesome :D
I hope they salvage a lot of them.
Yours,
Linus Walleij
next prev parent reply other threads:[~2018-05-02 12:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 12:10 [PATCH v2] pinctrl: msm: fix gpio-hog related boot issues Christian Lamparter
2018-04-02 15:04 ` Bjorn Andersson
2018-04-05 16:35 ` Christian Lamparter
2018-04-26 9:12 ` Linus Walleij
2018-04-26 21:47 ` Christian Lamparter
2018-05-02 12:14 ` Linus Walleij [this message]
2018-05-03 17:43 ` Christian Lamparter
2018-05-04 9:04 ` Laxman Dewangan
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=CACRpkdaEYFerKQa4QRCFEg2TOrdbnF6SfVZ9chLpmCxSUNcZBw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=chunkeey@gmail.com \
--cc=david.brown@linaro.org \
--cc=ldewangan@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=sven.eckelmann@openmesh.com \
--cc=swarren@wwwdotorg.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).