[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f5b6f47b-2a2d-a0c5-b777-9e4cb39ecf1d@baylibre.com>
Date: Mon, 21 Oct 2019 09:54:48 +0200
From: Neil Armstrong <narmstrong@...libre.com>
To: Christian Hewitt <christianshewitt@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Kevin Hilman <khilman@...libre.com>,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-amlogic@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] soc: amlogic: meson-gx-socinfo: Fix S905D3 ID for VIM3L
Hi,
On 21/10/2019 07:04, Christian Hewitt wrote:
> Chip on the board is S905D3 not S905X3.
>
> Fixes: 1d7c541b8a5b ("soc: amlogic: meson-gx-socinfo: Add S905X3 ID for VIM3L")
>
> Signed-off-by: Christian Hewitt <christianshewitt@...il.com>
> ---
> drivers/soc/amlogic/meson-gx-socinfo.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/soc/amlogic/meson-gx-socinfo.c b/drivers/soc/amlogic/meson-gx-socinfo.c
> index 87ed558..e612dae 100644
> --- a/drivers/soc/amlogic/meson-gx-socinfo.c
> +++ b/drivers/soc/amlogic/meson-gx-socinfo.c
> @@ -69,7 +69,7 @@ static const struct meson_gx_package_id {
> { "S922X", 0x29, 0x40, 0xf0 },
> { "A311D", 0x29, 0x10, 0xf0 },
> { "S905X3", 0x2b, 0x5, 0xf },
> - { "S905X3", 0x2b, 0xb0, 0xf2 },
> + { "S905D3", 0x2b, 0xb0, 0xf2 },
Why is the mask 0xf2 ? What is reported in dmesg ?
> { "A113L", 0x2c, 0x0, 0xf8 },
> };
>
>
Neil
Powered by blists - more mailing lists