From: Mark Brown <broonie@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Grant Likely <grant.likely@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Sven Van Asbroeck <thesven73@gmail.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Simon Han <z.han@kunbus.com>, Lukas Wunner <lukas@wunner.de>,
linux-spi <linux-spi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] spi: fix client driver breakages when using GPIO descriptors
Date: Tue, 24 Nov 2020 16:40:33 +0000 [thread overview]
Message-ID: <20201124164033.GH4933@sirena.org.uk> (raw)
In-Reply-To: <CACRpkdbJsiW_U2hrsT+t5gsbj+ow2t_kEmTQyD2jZxs3LCRfLw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]
On Tue, Nov 24, 2020 at 04:21:48PM +0100, Linus Walleij wrote:
> > What people think they were sold was the idea that they shouldn't have
> > to write driver code or upstream things, something with more AML like
> > capabilities (not realising that AML works partly because ACPI hugely
> > constrains system design).
> This makes a lot of sense.
> I suppose what we need to think about is the bigger question of why
> people/companies/managers are so worried about working upstream
> that they will go to lengths to avoid it and jump at any chance of
> raising a wall of abstraction between their internal development and
> the in-kernel software development.
> I think of this as vendor/community couples therapy or something,
> there is some form of deep disconnect or mistrust going on at times
> and having worked on both ends myself I would think I could
> understand it but I can't.
In this case I think this is partly due to the way people were sold on
the DT conversion - part of the sales pitch was that you'd not need to
get board support upstream, which is a useful thing if you want to run
things like LTS or distro kernels on newer hardware.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-11-24 16:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 15:07 [PATCH v1] spi: fix client driver breakages when using GPIO descriptors Sven Van Asbroeck
2020-11-09 14:25 ` Andy Shevchenko
2020-11-09 14:41 ` Sven Van Asbroeck
2020-11-11 1:05 ` Linus Walleij
2020-11-11 12:33 ` Mark Brown
2020-11-11 13:36 ` Linus Walleij
2020-11-16 21:06 ` Mark Brown
2020-11-18 1:03 ` Linus Walleij
2020-11-18 11:40 ` Mark Brown
2020-11-24 15:21 ` Linus Walleij
2020-11-24 16:40 ` Mark Brown [this message]
2020-11-25 9:19 ` Grant Likely
2020-11-25 9:17 ` Grant Likely
2020-11-11 1:08 ` Linus Walleij
2020-11-11 15:48 ` Mark Brown
2020-11-11 16:24 ` Sven Van Asbroeck
2020-11-11 16:32 ` Mark Brown
2020-11-12 11:41 ` Charles Keepax
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=20201124164033.GH4933@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=grant.likely@arm.com \
--cc=jonathan.cameron@huawei.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=robh+dt@kernel.org \
--cc=thesven73@gmail.com \
--cc=z.han@kunbus.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 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).