From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] soc: amlogic: Add Meson6/8/8b SoC Information driver
Date: Fri, 06 Oct 2017 15:38:13 -0700 [thread overview]
Message-ID: <7h60br9a22.fsf@baylibre.com> (raw)
In-Reply-To: <20170923141403.20882-1-martin.blumenstingl@googlemail.com> (Martin Blumenstingl's message of "Sat, 23 Sep 2017 16:14:00 +0200")
Martin Blumenstingl <martin.blumenstingl@googlemail.com> writes:
> The 32-bit Amlogic SoC have some registers which contain some information
> the SoC's major and version, as well as a "major version".
> This patchset adds support for this register decoding and exposing with the
> SoC bus infrastructure, with dt-bindings and DT node.
>
> This is inspired by Neil's Meson GX socinfo driver, see [0]
>
> All information was taken from Amlogic's 3.10 GPL kernel sources because
> the public S805 datasheet from Hardkernel does not contain any relevant
> information for these register blocks.
>
>
> [0] http://lists.infradead.org/pipermail/linux-amlogic/2017-June/004187.html
>
> Martin Blumenstingl (3):
> dt-bindings: Amlogic: add documentation for the SoC info register
> areas
Applied to v4.15/dt
> soc: amlogic: Add Meson6/Meson8/Meson8b/Meson8m2 SoC Information
> driver
Applied to v4.15/drivers
> ARM: dts: meson: add SoC information nodes
Applied to v4.15/dt
Thanks,
Kevin
prev parent reply other threads:[~2017-10-06 22:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-23 14:14 [PATCH 0/3] soc: amlogic: Add Meson6/8/8b SoC Information driver Martin Blumenstingl
2017-09-23 14:14 ` [PATCH 1/3] dt-bindings: Amlogic: add documentation for the SoC info register areas Martin Blumenstingl
2017-10-05 19:52 ` Rob Herring
2017-09-23 14:14 ` [PATCH 2/3] soc: amlogic: Add Meson6/Meson8/Meson8b/Meson8m2 SoC Information driver Martin Blumenstingl
2017-09-23 14:14 ` [PATCH 3/3] ARM: dts: meson: add SoC information nodes Martin Blumenstingl
2017-10-06 22:38 ` Kevin Hilman [this message]
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=7h60br9a22.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.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).