From: Linus Walleij <linus.walleij@linaro.org>
To: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
dev@lists.96boards.org
Cc: Mark Rutland <mark.rutland@arm.com>,
Arnd Bergmann <arnd@arndb.de>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
Michal Simek <michal.simek@xilinx.com>,
Rob Herring <robh+dt@kernel.org>, Mark Brown <broonie@kernel.org>,
John Stultz <john.stultz@linaro.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Frank Rowand <frowand.list@gmail.com>,
Andy Shevchenko <andy@infradead.org>
Subject: [PATCH 0/4 v1] Mezzanine Low Speed connector bus
Date: Thu, 23 Aug 2018 12:33:28 +0200 [thread overview]
Message-ID: <20180823103332.32047-1-linus.walleij@linaro.org> (raw)
I have been a bit hesitant to reiterate the series, but this is
anyways a v1 of the 96Boards Mezzanine Low Speed connector
driver framework.
I know the boards have a high speed connector as well, just
trying to work stepwise and do the simple things first.
What convinced me to continue was very real usecases that exist
today, as this makes the secure96 Mezzanine work:
- Get something upstream that makes it possible to without
any trouble or extensive ugly hacking probe and use the
secure96 mezzanine. This is motivated by the IoT design
space which needs a way to plug in proper security and the
secure96 offers a TPM chip for root of trust and key
handling.
- A clear indication that the same approach will work just
as fine with ACPI without reinventing the universe. I do
not have a definitive proof of this, but it is more
plausible that this will be reusable for ACPI than any of
the DT-centric ideas I've seen for populating
daughterboards. There are 96boards using ACPI today.
A secure96 TPM is desireable for things like the ARM
developer box which has this LS connector:
https://www.96boards.org/product/developerbox/
- Some indication that binding the connector like this will
not implicate or screw things up for the DT-overlays
idea, i.e. a both/and and not either/or approach.
The idea is for this to go upstream through ARM SoC the day
noone actively NACK it and someone actively ACK it. Expect
some more iterations.
Linus Walleij (4):
eeprom: at24: Allow passing gpiodesc from pdata
spi: Make of_find_spi_device_by_node() available
bus: Add DT bindings for 96Boards low speed connector
bus: 96boards Low-Speed Connector
.../bus/96boards,low-speed-connector.txt | 50 +++
drivers/bus/Kconfig | 2 +
drivers/bus/Makefile | 4 +-
drivers/bus/daughterboards/96boards-ls-bus.c | 39 ++
.../daughterboards/96boards-ls-connector.c | 367 ++++++++++++++++++
.../bus/daughterboards/96boards-mezzanines.h | 77 ++++
.../bus/daughterboards/96boards-secure96.c | 265 +++++++++++++
drivers/bus/daughterboards/Kconfig | 50 +++
drivers/bus/daughterboards/Makefile | 6 +
drivers/misc/eeprom/at24.c | 6 +-
drivers/spi/spi.c | 33 +-
include/linux/platform_data/at24.h | 2 +
include/linux/spi/spi.h | 4 +
13 files changed, 888 insertions(+), 17 deletions(-)
create mode 100644 Documentation/devicetree/bindings/bus/96boards,low-speed-connector.txt
create mode 100644 drivers/bus/daughterboards/96boards-ls-bus.c
create mode 100644 drivers/bus/daughterboards/96boards-ls-connector.c
create mode 100644 drivers/bus/daughterboards/96boards-mezzanines.h
create mode 100644 drivers/bus/daughterboards/96boards-secure96.c
create mode 100644 drivers/bus/daughterboards/Kconfig
create mode 100644 drivers/bus/daughterboards/Makefile
--
2.17.0
next reply other threads:[~2018-08-23 10:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 10:33 Linus Walleij [this message]
2018-08-23 10:33 ` [PATCH 1/4] eeprom: at24: Allow passing gpiodesc from pdata Linus Walleij
2018-08-23 11:14 ` Bartosz Golaszewski
2018-08-23 10:33 ` [PATCH 2/4] spi: Make of_find_spi_device_by_node() available Linus Walleij
2018-08-23 10:33 ` [PATCH 3/4] bus: Add DT bindings for 96Boards low speed connector Linus Walleij
2018-08-23 13:45 ` Rob Herring
2018-09-05 9:05 ` Linus Walleij
2018-08-23 10:33 ` [PATCH 4/4] bus: 96boards Low-Speed Connector Linus Walleij
2018-08-23 23:06 ` [PATCH 0/4 v1] Mezzanine Low Speed connector bus Frank Rowand
2018-08-24 7:28 ` Linus Walleij
2018-11-15 16:26 ` Frank Rowand
2018-11-15 22:59 ` Linus Walleij
2018-11-16 0:16 ` 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=20180823103332.32047-1-linus.walleij@linaro.org \
--to=linus.walleij@linaro.org \
--cc=andy@infradead.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=dev@lists.96boards.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=john.stultz@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mark.rutland@arm.com \
--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).