From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: Neil Armstrong <narmstrong@baylibre.com>,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] arm64: Add support for Amlogic SM1 SoC Family
Date: Tue, 20 Aug 2019 12:25:19 -0700 [thread overview]
Message-ID: <7h4l2bej1c.fsf@baylibre.com> (raw)
In-Reply-To: <20190820144052.18269-1-narmstrong@baylibre.com>
Neil Armstrong <narmstrong@baylibre.com> writes:
> The new Amlogic SM1 SoC Family is a derivative of the Amlogic G12A
> SoC Family, with the following changes :
> - Cortex-A55 cores instead of A53
> - more power domains, including USB & PCIe
> - a neural network co-processor (NNA)
> - a CSI input and image processor
> - some changes in the audio complex, thus not yet enabled
> - new clocks, for NNA, CSI and a clock tree for each CPU Core
>
> This serie does not add support for NNA, CSI, Audio, USB, Display
> or DVFS, it only aligns with the current G12A Support.
>
> With this serie, the SEI610 Board has supported :
> - Default-boot CPU frequency
> - Ethernet
> - LEDs
> - IR
> - GPIO Buttons
> - eMMC
> - SDCard
> - SDIO WiFi
> - UART Bluetooth
>
> Audio (HDMI, Embedded HP, MIcs), USB, HDMI, IR Output, & RGB Led
> would be supported in following patchsets.
>
> Dependencies:
> - g12-common.dtsi from the DVFS patchset at [1]
>
> Changes from rfc at [2]:
> - Removed Power domain patches & display/USB support, will resend separately
> - Removed applied AO-CEC patches
> - Fixed clk-measure IDs
> - Collected reviewed-by tags
>
> [1] https://patchwork.kernel.org/cover/11025309/
> [2] https://patchwork.kernel.org/cover/11025511/
Series queued for v5.4...
> Neil Armstrong (6):
> soc: amlogic: meson-gx-socinfo: Add SM1 and S905X3 IDs
> dt-bindings: soc: amlogic: clk-measure: Add SM1 compatible
> soc: amlogic: clk-measure: Add support for SM1
... these 3 in v5.4/drivers ...
> dt-bindings: arm: amlogic: add SM1 bindings
> dt-bindings: arm: amlogic: add SEI Robotics SEI610 bindings
> arm64: dts: add support for SM1 based SEI Robotics SEI610
... and these 3 in v5.4/dt64 with Rob's tag.
Thanks,
Kevin
next prev parent reply other threads:[~2019-08-20 19:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 14:40 [PATCH 0/6] arm64: Add support for Amlogic SM1 SoC Family Neil Armstrong
2019-08-20 14:40 ` [PATCH 1/6] soc: amlogic: meson-gx-socinfo: Add SM1 and S905X3 IDs Neil Armstrong
2019-08-20 14:40 ` [PATCH 2/6] dt-bindings: soc: amlogic: clk-measure: Add SM1 compatible Neil Armstrong
2019-08-20 14:40 ` [PATCH 3/6] soc: amlogic: clk-measure: Add support for SM1 Neil Armstrong
2019-08-20 14:40 ` [PATCH 4/6] dt-bindings: arm: amlogic: add SM1 bindings Neil Armstrong
2019-08-20 16:15 ` Rob Herring
2019-08-20 14:40 ` [PATCH 5/6] dt-bindings: arm: amlogic: add SEI Robotics SEI610 bindings Neil Armstrong
2019-08-20 16:16 ` Rob Herring
2019-08-20 14:40 ` [PATCH 6/6] arm64: dts: add support for SM1 based SEI Robotics SEI610 Neil Armstrong
2019-08-20 20:11 ` Martin Blumenstingl
2019-08-20 20:32 ` Kevin Hilman
2019-08-20 19:25 ` Kevin Hilman [this message]
2019-08-20 23:06 ` [PATCH 0/6] arm64: Add support for Amlogic SM1 SoC Family 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=7h4l2bej1c.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
/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).