From: Rob Herring <robh@kernel.org>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
narmstrong@baylibre.com, khilman@baylibre.com,
yixun.lan@amlogic.com, carlo@caione.org,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, jbrunet@baylibre.com
Subject: Re: [RfC v1 2/5] dt-bindings: arm: amlogic: Add support for GXL S905W and the P281 board
Date: Mon, 25 Jun 2018 15:03:24 -0600 [thread overview]
Message-ID: <20180625210324.GA4412@rob-hp-laptop> (raw)
In-Reply-To: <20180624182814.31691-3-martin.blumenstingl@googlemail.com>
On Sun, Jun 24, 2018 at 08:28:11PM +0200, Martin Blumenstingl wrote:
> S905W SoC is another SoC from the GXL family. It is a cost-reduced
> version of the S905X SoC. The following differences are known:
> - S905W supports HDMI resolutions up to 4k@30fps (while S905X support
> resolutions up to 4k@60fps)
> - the built-in video decoders of S905W decode up to 4k@30fps (while
> S905X supports decoding up to 4k@60fps)
> - CPU speed on S905W is limited to 1.2GHz (compared to 1.5GHz on S905X,
> this is handled in the SCPI firmware)
> - the DRAM interface on S905W is limited to 16-bit (GXL supports both,
> 16-bit and 32-bit)
>
> Notes based on Amlogic's GPL kernel sources:
> - the P281 is a development board from Amlogic which uses the S905W SoC.
> Amlogic's GPL kernel sources indicate that it uses the same PCB layout
> as the "P231" board (and simply replaces the S905D from the original
> P231 board with a S905W SoC).
> - it is assumed that the S905W SoC is pin-compatible with the S905X SoC
> since Amlogic's GPL kernel sources use the same driver for both SoCs.
> - gxl_p281_1g.dts contains a comment which mentions that "max gp pll for
> gpu is 650M, temporarily disabled". However, it seems to boot fine
> with 744MHz (as used on GXBB and the other GXL SoCs).
>
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> ---
> Documentation/devicetree/bindings/arm/amlogic.txt | 6 ++++++
> 1 file changed, 6 insertions(+)
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2018-06-25 21:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-24 18:28 [RfC v1 0/5] ARM64: amlogic: add support for the S905W and two boards Martin Blumenstingl
2018-06-24 18:28 ` [RfC v1 1/5] dt-bindings: add vendor prefix for Shenzhen Oranth Technology Co., Ltd Martin Blumenstingl
2018-06-25 21:01 ` Rob Herring
2018-06-24 18:28 ` [RfC v1 2/5] dt-bindings: arm: amlogic: Add support for GXL S905W and the P281 board Martin Blumenstingl
2018-06-25 21:03 ` Rob Herring [this message]
2018-06-24 18:28 ` [RfC v1 3/5] dt-bindings: arm: amlogic: Add support for the Oranth Tanix TX3 Mini Martin Blumenstingl
2018-06-25 21:03 ` Rob Herring
2018-06-24 18:28 ` [RfC v1 4/5] ARM64: dts: meson-gxl: add support for the S905W SoC and the P281 board - WiP Martin Blumenstingl
2018-06-25 12:51 ` Neil Armstrong
2018-06-25 17:25 ` Martin Blumenstingl
2018-06-29 21:50 ` Kevin Hilman
2018-06-24 18:28 ` [RfC v1 5/5] ARM64: dts: meson-gxl: add support for the Oranth Tanix TX3 Mini Martin Blumenstingl
2018-06-29 21:53 ` 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=20180625210324.GA4412@rob-hp-laptop \
--to=robh@kernel.org \
--cc=carlo@caione.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.com \
--cc=yixun.lan@amlogic.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