u-boot-amlogic.groups.io archive mirror
 help / color / mirror / Atom feed
From: "Neil Armstrong" <narmstrong@baylibre.com>
To: Christian Hewitt <christianshewitt@gmail.com>,
	u-boot@lists.denx.de, u-boot-amlogic@groups.io,
	linux-amlogic@lists.infradead.org
Subject: Re: [PATCH] ARM: meson: Add S905Y2 SOC ID
Date: Mon, 30 Aug 2021 09:53:06 +0200	[thread overview]
Message-ID: <06547fcd-2881-3601-d02f-77df56b9a258@baylibre.com> (raw)
In-Reply-To: <20210820021836.1024-1-christianshewitt@gmail.com>

On 20/08/2021 04:18, Christian Hewitt wrote:
> Add the SOC ID for the S905Y2 to board info, see below for before/after
> tested with a Radxa Zero board:
> 
> SoC:   Amlogic Meson G12A (Unknown) Revision 28:b (30:2)
> SoC:   Amlogic Meson G12A (S905Y2) Revision 28:b (30:2)
> 
> Signed-off-by: Christian Hewitt <christianshewitt@gmail.com>
> ---
>  arch/arm/mach-meson/board-info.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/arch/arm/mach-meson/board-info.c b/arch/arm/mach-meson/board-info.c
> index d16d3f194d..2421acd817 100644
> --- a/arch/arm/mach-meson/board-info.c
> +++ b/arch/arm/mach-meson/board-info.c
> @@ -64,6 +64,7 @@ static const struct meson_gx_package_id {
>  	{ "A113X",  0x25, 0x37, 0xff },
>  	{ "A113D",  0x25, 0x22, 0xff },
>  	{ "S905D2", 0x28, 0x10, 0xf0 },
> +	{ "S905Y2", 0x28, 0x30, 0xf0 },
>  	{ "S905X2", 0x28, 0x40, 0xf0 },
>  	{ "A311D",  0x29, 0x10, 0xf0 },
>  	{ "S922X",  0x29, 0x40, 0xf0 },
> 

Reviewed-by: Neil Armstrong <narmstrong@baylibre.com>

       reply	other threads:[~2021-08-30  7:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210820021836.1024-1-christianshewitt@gmail.com>
2021-08-30  7:53 ` Neil Armstrong [this message]
2021-08-30  7:55 ` [PATCH] ARM: meson: Add S905Y2 SOC ID Neil Armstrong

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=06547fcd-2881-3601-d02f-77df56b9a258@baylibre.com \
    --to=narmstrong@baylibre.com \
    --cc=christianshewitt@gmail.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=u-boot-amlogic@groups.io \
    --cc=u-boot@lists.denx.de \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).