From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Chanho Park <chanho61.park@samsung.com>,
Rob Herring <robh+dt@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>
Cc: Tomasz Figa <tomasz.figa@gmail.com>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 3/3] arm64: dts: exynos: add minimal support for exynosautov9 sadk board
Date: Sat, 9 Oct 2021 20:24:34 +0200 [thread overview]
Message-ID: <ddea428e-b756-ec75-5cb6-33226c900259@canonical.com> (raw)
In-Reply-To: <20211008091443.44625-4-chanho61.park@samsung.com>
On 08/10/2021 11:14, Chanho Park wrote:
> SADK(Samsung Automotive Development Kit) is the development kit to
> evaluate Exynos Auto v9 SoC. It has 16GB LPDDR4 DRAM and two
> 256GB Samsung UFS. This patch enables only serial console and ufs0
> device.
>
> Signed-off-by: Chanho Park <chanho61.park@samsung.com>
> ---
> .../bindings/arm/samsung/samsung-boards.yaml | 6 ++
> arch/arm64/boot/dts/exynos/Makefile | 3 +-
> .../boot/dts/exynos/exynosautov9-sadk.dts | 56 +++++++++++++++++++
> 3 files changed, 64 insertions(+), 1 deletion(-)
> create mode 100644 arch/arm64/boot/dts/exynos/exynosautov9-sadk.dts
>
> diff --git a/Documentation/devicetree/bindings/arm/samsung/samsung-boards.yaml b/Documentation/devicetree/bindings/arm/samsung/samsung-boards.yaml
> index 0796f0c87727..ef6dc14be4b5 100644
> --- a/Documentation/devicetree/bindings/arm/samsung/samsung-boards.yaml
> +++ b/Documentation/devicetree/bindings/arm/samsung/samsung-boards.yaml
> @@ -199,6 +199,12 @@ properties:
> - samsung,exynos7-espresso # Samsung Exynos7 Espresso
> - const: samsung,exynos7
>
> + - description: Exynos Auto v9 based boards
> + items:
> + - enum:
> + - samsung,exynosautov9-sadk # Samsung Exynos Auto v9 SADK
> + - const: samsung,exynosautov9
> +
> required:
> - compatible
>
This looks good, but depends on fixes in patch #2.
Best regards,
Krzysztof
prev parent reply other threads:[~2021-10-09 18:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20211008091639epcas2p443a12d674adbb34aa5771cae2c0659fe@epcas2p4.samsung.com>
2021-10-08 9:14 ` [PATCH v2 0/3] add initial support for exynosautov9 Chanho Park
[not found] ` <CGME20211008091639epcas2p28339f2f73755a3c842fbb95f313bf7d9@epcas2p2.samsung.com>
2021-10-08 9:14 ` [PATCH v2 1/3] pinctrl: samsung: support ExynosAutov9 SoC pinctrl Chanho Park
2021-10-09 18:25 ` (subset) " Krzysztof Kozlowski
[not found] ` <CGME20211008091640epcas2p1fde9bedf5492db3f35207d118e5d9123@epcas2p1.samsung.com>
2021-10-08 9:14 ` [PATCH v2 2/3] arm64: dts: exynos: add initial support for exynosautov9 SoC Chanho Park
2021-10-09 18:23 ` Krzysztof Kozlowski
[not found] ` <CGME20211008091640epcas2p280fb1bce16ebff863f6ae4db66b2b240@epcas2p2.samsung.com>
2021-10-08 9:14 ` [PATCH v2 3/3] arm64: dts: exynos: add minimal support for exynosautov9 sadk board Chanho Park
2021-10-09 18:24 ` Krzysztof Kozlowski [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=ddea428e-b756-ec75-5cb6-33226c900259@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=chanho61.park@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=tomasz.figa@gmail.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).