From: <Claudiu.Beznea@microchip.com>
To: <Nicolas.Ferre@microchip.com>,
<linux-arm-kernel@lists.infradead.org>,
<alexandre.belloni@bootlin.com>
Cc: <linux-kernel@vger.kernel.org>, <Mihai.Sain@microchip.com>
Subject: Re: [PATCH] ARM: at91: add support in soc driver for new SAMA5D29
Date: Thu, 3 Mar 2022 08:19:37 +0000 [thread overview]
Message-ID: <63d5bc08-7681-954a-2106-2653abf76b57@microchip.com> (raw)
In-Reply-To: <20220302155329.27668-1-nicolas.ferre@microchip.com>
On 02.03.2022 17:53, nicolas.ferre@microchip.com wrote:
> From: Mihai Sain <mihai.sain@microchip.com>
>
> Add detection of new SAMA5D29 by the SoC driver.
>
> Signed-off-by: Mihai Sain <mihai.sain@microchip.com>
> Signed-off-by: Nicolas Ferre <nicolas.ferre@microchip.com>
Reviewed-by: Claudiu Beznea <claudiu.beznea@microchip.com>
> ---
> drivers/soc/atmel/soc.c | 3 +++
> drivers/soc/atmel/soc.h | 1 +
> 2 files changed, 4 insertions(+)
>
> diff --git a/drivers/soc/atmel/soc.c b/drivers/soc/atmel/soc.c
> index a490ad7e090f..b2d365ae0282 100644
> --- a/drivers/soc/atmel/soc.c
> +++ b/drivers/soc/atmel/soc.c
> @@ -156,6 +156,9 @@ static const struct at91_soc socs[] __initconst = {
> AT91_SOC(SAMA5D2_CIDR_MATCH, AT91_CIDR_MATCH_MASK,
> AT91_CIDR_VERSION_MASK, SAMA5D28C_LD2G_EXID_MATCH,
> "sama5d28c 256MiB LPDDR2 SiP", "sama5d2"),
> + AT91_SOC(SAMA5D2_CIDR_MATCH, AT91_CIDR_MATCH_MASK,
> + AT91_CIDR_VERSION_MASK, SAMA5D29CN_EXID_MATCH,
> + "sama5d29", "sama5d2"),
> AT91_SOC(SAMA5D3_CIDR_MATCH, AT91_CIDR_MATCH_MASK,
> AT91_CIDR_VERSION_MASK, SAMA5D31_EXID_MATCH,
> "sama5d31", "sama5d3"),
> diff --git a/drivers/soc/atmel/soc.h b/drivers/soc/atmel/soc.h
> index c3eb3c8f0834..2ecaa75b00f0 100644
> --- a/drivers/soc/atmel/soc.h
> +++ b/drivers/soc/atmel/soc.h
> @@ -95,6 +95,7 @@ at91_soc_init(const struct at91_soc *socs);
> #define SAMA5D28C_LD2G_EXID_MATCH 0x00000072
> #define SAMA5D28CU_EXID_MATCH 0x00000010
> #define SAMA5D28CN_EXID_MATCH 0x00000020
> +#define SAMA5D29CN_EXID_MATCH 0x00000023
>
> #define SAMA5D3_CIDR_MATCH 0x0a5c07c0
> #define SAMA5D31_EXID_MATCH 0x00444300
next prev parent reply other threads:[~2022-03-03 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 15:53 nicolas.ferre
2022-03-03 8:19 ` Claudiu.Beznea [this message]
2022-03-04 11:49 ` Nicolas Ferre
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=63d5bc08-7681-954a-2106-2653abf76b57@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Mihai.Sain@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®