From: Davide Ciminaghi <ciminaghi@gnudd.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Alexandre Courbot <gnurou@gmail.com>,
Alexandre Courbot <acourbot@nvidia.com>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Jonathan Corbet <corbet@lwn.net>,
Russell King <linux@armlinux.org.uk>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"moderated list:ARM PORT" <linux-arm-kernel@lists.infradead.org>,
"open list:GENERIC INCLUDE/ASM HEADER FILES"
<linux-arch@vger.kernel.org>,
Alessandro Rubini <rubini@gnudd.com>
Subject: Re: [PATCH] gpio: Allow user to customise maximum number of GPIOs
Date: Wed, 31 Aug 2022 16:12:36 +0200 [thread overview]
Message-ID: <Yw9sVCNtaLUjZH/F@arcana.i.gnudd.com> (raw)
In-Reply-To: <CACRpkdZeAAZYqV3ccd-X=ZwdnfSwRUdXchGETB-WTkgSZQL=Pw@mail.gmail.com>
On Wed, Aug 31, 2022 at 03:32:25PM +0200, Linus Walleij wrote:
> On Tue, Aug 30, 2022 at 9:58 AM Davide Ciminaghi <ciminaghi@gnudd.com> wrote:
>
> > the sta2x11 was a chip containing AMBA peripherals and a PCIe to AMBA bridge
> > (it is still in production as far as I know, but deprecated for new designs).
> > It would typically be installed on x86 machines, so you needed to build and
> > run AMBA drivers in an x86 environment. The original drivers we started from
> > had platform data, but then we were told to switch to DTS.
>
> For the record I think that was bad advice, I hope it wasn't me.
> But the world was different back then I suppose.
> Adding DTS to x86 which is inherently ACPI is not a good idea.
> Especially if you look at how SBSA ACPI UARTS were done
> in drivers/tty/serial/amba-pl011.c.
>
now that I think of it, ACPI was also listed as a possible choice, but the
problem was that we didn't know much about ACPI, and took the DTS way.
So there was no bad advice, just fear of the unknown :-)
Thanks
Davide
next prev parent reply other threads:[~2022-08-31 14:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 10:40 [PATCH] gpio: Allow user to customise maximum number of GPIOs Christophe Leroy
2022-08-11 19:57 ` H. Peter Anvin
2022-08-12 21:58 ` Andy Shevchenko
2022-08-12 23:21 ` H. Peter Anvin
2022-08-17 17:21 ` Christophe Leroy
2022-08-17 17:46 ` Arnd Bergmann
2022-08-18 6:00 ` Christophe Leroy
2022-08-18 8:25 ` Arnd Bergmann
2022-08-18 9:33 ` Linus Walleij
2022-08-18 9:47 ` Arnd Bergmann
2022-08-18 11:13 ` Linus Walleij
2022-08-18 11:33 ` Arnd Bergmann
2022-08-18 12:25 ` Linus Walleij
2022-08-18 12:46 ` Arnd Bergmann
2022-08-18 13:11 ` Christophe Leroy
2022-08-25 13:36 ` Linus Walleij
2022-08-25 14:00 ` Christophe Leroy
2022-08-26 13:49 ` Linus Walleij
2022-08-26 15:08 ` Christophe Leroy
2022-08-26 21:54 ` Linus Walleij
2022-08-28 9:06 ` Christophe Leroy
2022-08-28 10:04 ` Arnd Bergmann
2022-08-30 7:58 ` Davide Ciminaghi
2022-08-31 13:32 ` Linus Walleij
2022-08-31 14:12 ` Davide Ciminaghi [this message]
2022-08-31 21:07 ` Andy Shevchenko
2022-08-31 21:48 ` Davide Ciminaghi
2022-08-30 8:33 ` Alessandro Rubini
2022-08-30 9:03 ` Christophe Leroy
2022-08-28 11:35 ` Linus Walleij
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=Yw9sVCNtaLUjZH/F@arcana.i.gnudd.com \
--to=ciminaghi@gnudd.com \
--cc=acourbot@nvidia.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=brgl@bgdev.pl \
--cc=christophe.leroy@csgroup.eu \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=gnurou@gmail.com \
--cc=hpa@zytor.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mingo@redhat.com \
--cc=rubini@gnudd.com \
--cc=tglx@linutronix.de \
--cc=x86@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).