mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: narmstrong@baylibre.com (Neil Armstrong)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v3.1 0/3] soc: amlogic: Add Amlogic SoC Information driver
Date: Thu, 13 Jul 2017 12:25:20 +0200	[thread overview]
Message-ID: <e9558b4f-b155-9f25-fe39-b876973299b5@baylibre.com> (raw)
In-Reply-To: <CAFBinCAK0iXJ5zLg64oABXs7rno48Dni6Zc2dQ3_aadJS7wiSQ@mail.gmail.com>

On 07/12/2017 09:03 PM, Martin Blumenstingl wrote:
> Hi Kevin,
> 
> On Fri, Jun 23, 2017 at 10:28 AM, Neil Armstrong
> <narmstrong@baylibre.com> wrote:
>> Amlogic SoCs have a SoC information register for SoC type, package type and
>> revision information.
>> This patchset adds support for this register decoding and exposing with the
>> SoC bus infrastructure, with dt-bindings and DT node.
> I'm curious: are you going to take this through your tree or are we
> waiting for someone's ACK here?

I'm curious also, it should go through armsoc-drivers, no ?

Neil

> 
>> Changes since v3.1 at [3] :
>>  - Prepend amlogic to has-chip-id property
>>
>> Changes since v2 at [2] :
>>  - Removed subnodes of socinfo node
>>  - Checks has-chip-id property and if node is enabled
>>
>> Changes since v1 at [1] :
>>  - Switch DT representation to use regmap ans sub-node of a simple-mfd node
>>  - Updated DT, bindings and driver accordingly
>>
>> [1] http://lkml.kernel.org/r/1490950079-10145-1-git-send-email-narmstrong at baylibre.com
>> [2] http://lkml.kernel.org/r/1496742340-10307-1-git-send-email-narmstrong at baylibre.com
>> [3] http://lkml.kernel.org/r/1497441946-24379-1-git-send-email-narmstrong at baylibre.com
>>
>> Neil Armstrong (3):
>>   dt-bindings: arm: amlogic: Add SoC information bindings
>>   ARM64: dts: meson-gx: Add SoC info register
>>   soc: Add Amlogic SoC Information driver
>>
>>  Documentation/devicetree/bindings/arm/amlogic.txt |  29 ++++
>>  arch/arm64/boot/dts/amlogic/meson-gx.dtsi         |   6 +
>>  drivers/soc/Kconfig                               |   1 +
>>  drivers/soc/Makefile                              |   1 +
>>  drivers/soc/amlogic/Kconfig                       |  12 ++
>>  drivers/soc/amlogic/Makefile                      |   1 +
>>  drivers/soc/amlogic/meson-gx-socinfo.c            | 177 ++++++++++++++++++++++
>>  7 files changed, 227 insertions(+)
>>  create mode 100644 drivers/soc/amlogic/Kconfig
>>  create mode 100644 drivers/soc/amlogic/Makefile
>>  create mode 100644 drivers/soc/amlogic/meson-gx-socinfo.c
>>
>> --
>> 1.9.1
>>
>>
>> _______________________________________________
>> linux-amlogic mailing list
>> linux-amlogic at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-amlogic

  reply	other threads:[~2017-07-13 10:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23  8:28 Neil Armstrong
2017-06-23  8:28 ` [PATCH v3.1 1/3] dt-bindings: arm: amlogic: Add SoC information bindings Neil Armstrong
2017-06-23  8:28 ` [PATCH v3.1 2/3] ARM64: dts: meson-gx: Add SoC info register Neil Armstrong
2017-06-23  8:28 ` [PATCH v3.1 3/3] soc: Add Amlogic SoC Information driver Neil Armstrong
2017-07-12 19:03 ` [PATCH v3.1 0/3] soc: amlogic: " Martin Blumenstingl
2017-07-13 10:25   ` Neil Armstrong [this message]
2017-07-28  0:29     ` Kevin Hilman

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=e9558b4f-b155-9f25-fe39-b876973299b5@baylibre.com \
    --to=narmstrong@baylibre.com \
    --cc=linus-amlogic@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

all inboxes | Powered by JetHome®