From: Mark Brown <broonie@kernel.org>
To: Daniel Thompson <daniel.thompson@linaro.org>
Cc: devicetree@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Frank Rowand <frowand.list@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Michal Simek <michal.simek@xilinx.com>,
dev@lists.96boards.org, Rob Herring <robh+dt@kernel.org>,
Andy Shevchenko <andy@infradead.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [Dev] [PATCH 0/5] RFC: Mezzanine handling for 96boards
Date: Tue, 19 Jun 2018 12:56:08 +0100 [thread overview]
Message-ID: <20180619115608.GA11230@sirena.org.uk> (raw)
In-Reply-To: <20180619111018.r3m35g4ei6625pqz@holly.lan>
[-- Attachment #1.1: Type: text/plain, Size: 1167 bytes --]
On Tue, Jun 19, 2018 at 12:10:18PM +0100, Daniel Thompson wrote:
> On Mon, Jun 18, 2018 at 09:45:51AM +0200, Linus Walleij wrote:
> > - I am especially curious about input from Andy and Mika from
> > the Intel/ACPI camp on what they have seen for non-discoverable
> > plug-in boards. Does this problem even exist in the Intel
> > world, or not...
> I'm also interested in the "what about ACPI" question?
> Using C makes describing a board in ACPI fairly easy. AFAICT allocating
> IDs to a board rather than its included components is fairly natural for
> ACPI.
Yes, they have this problem - they have plug in modules on for example
the minnowboard and some of their other reference platforms. They have
overlays working for ACPI, these have their own problems in that they
don't appear to have the equivalent of DMI data (at least the patches
people are sending indicates that they don't) which is unfortuate as the
idiomatic thing for ACPI is as you say to key huge chunks of data of
quirk tables based on the DMI information for their boards.
They don't to my knowledge have generic connectors or anything like
that, it's just patches to the base ACPI.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-06-19 11:56 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 7:45 [PATCH 0/5] RFC: Mezzanine handling for 96boards Linus Walleij
2018-06-18 7:45 ` [PATCH 1/5] RFC: gpio: Add API to explicitly name a consumer Linus Walleij
2018-06-18 7:45 ` [PATCH 2/5] RFC: eeprom: at24: Allow passing gpiodesc from pdata Linus Walleij
2018-06-20 0:45 ` Andy Shevchenko
2018-06-18 7:45 ` [PATCH 3/5] RFC: spi: Make of_find_spi_device_by_node() available Linus Walleij
2018-06-18 7:45 ` [PATCH 4/5] RFC: bus: 96boards Low-Speed Connector Linus Walleij
2018-06-19 11:19 ` [Dev] " Daniel Thompson
2018-06-18 7:45 ` [PATCH 5/5] RFC: ARM64: dts: Add Low-Speed Connector to ZCU100 Linus Walleij
2018-06-19 14:55 ` Rob Herring
2018-06-22 13:22 ` Michal Simek
2018-06-18 12:21 ` [PATCH 0/5] RFC: Mezzanine handling for 96boards Arnd Bergmann
2018-06-18 13:22 ` Ard Biesheuvel
2018-06-18 14:15 ` Arnd Bergmann
2018-06-22 13:36 ` Michal Simek
2018-06-19 15:14 ` [Dev] " Yang Zhang
2018-06-19 15:25 ` Ard Biesheuvel
2018-06-19 15:26 ` Yang Zhang
2018-06-19 15:30 ` Ard Biesheuvel
2018-06-19 15:32 ` Yang Zhang
2018-06-22 13:08 ` Michal Simek
2018-06-26 9:10 ` Linus Walleij
2018-06-26 8:09 ` Linus Walleij
2018-06-26 8:19 ` Ard Biesheuvel
2018-06-26 8:36 ` Linus Walleij
2018-06-26 8:02 ` Linus Walleij
2018-06-26 8:08 ` Arnd Bergmann
2018-06-26 12:12 ` Mark Brown
2018-07-16 15:07 ` Rob Herring
2018-06-19 11:10 ` [Dev] " Daniel Thompson
2018-06-19 11:56 ` Mark Brown [this message]
2018-06-19 15:52 ` Rob Herring
2018-06-21 13:02 ` Frank Rowand
2018-06-26 9:03 ` Linus Walleij
2018-06-26 9:00 ` Linus Walleij
2018-06-27 15:23 ` [Dev] " Rob Herring
2018-06-28 6:10 ` Michal Simek
2018-06-21 12:58 ` Frank Rowand
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=20180619115608.GA11230@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andy@infradead.org \
--cc=arnd@arndb.de \
--cc=daniel.thompson@linaro.org \
--cc=dev@lists.96boards.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=michal.simek@xilinx.com \
--cc=mika.westerberg@linux.intel.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).