From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Claudiu Beznea <claudiu.beznea@microchip.com>,
<robh+dt@kernel.org>, <alexandre.belloni@bootlin.com>,
<ludovic.desroches@microchip.com>
Cc: <sandeepsheriker.mallikarjun@microchip.com>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] ARM: dts: at91: sama5d2: map securam as device
Date: Wed, 2 Dec 2020 11:27:45 +0100 [thread overview]
Message-ID: <c27ce6d6-ee64-af8b-7cd7-2f263653b5f9@microchip.com> (raw)
In-Reply-To: <1606903025-14197-3-git-send-email-claudiu.beznea@microchip.com>
On 02/12/2020 at 10:57, Claudiu Beznea wrote:
> Due to strobe signal not being propagated from CPU to securam
> the securam needs to be mapped as device or strongly ordered memory
> to work properly. Otherwise, updating to one offset may affect
> the adjacent locations in securam.
>
> Fixes: d4ce5f44d4409 ("ARM: dts: at91: sama5d2: Add securam node")
> Signed-off-by: Claudiu Beznea <claudiu.beznea@microchip.com>
Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
> ---
> arch/arm/boot/dts/sama5d2.dtsi | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/boot/dts/sama5d2.dtsi b/arch/arm/boot/dts/sama5d2.dtsi
> index 2ddc85dff8ce..6d399ac0385d 100644
> --- a/arch/arm/boot/dts/sama5d2.dtsi
> +++ b/arch/arm/boot/dts/sama5d2.dtsi
> @@ -656,6 +656,7 @@
> clocks = <&pmc PMC_TYPE_PERIPHERAL 51>;
> #address-cells = <1>;
> #size-cells = <1>;
> + no-memory-wc;
> ranges = <0 0xf8044000 0x1420>;
> };
>
>
--
Nicolas Ferre
WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Claudiu Beznea <claudiu.beznea@microchip.com>,
<robh+dt@kernel.org>, <alexandre.belloni@bootlin.com>,
<ludovic.desroches@microchip.com>
Cc: devicetree@vger.kernel.org,
sandeepsheriker.mallikarjun@microchip.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] ARM: dts: at91: sama5d2: map securam as device
Date: Wed, 2 Dec 2020 11:27:45 +0100 [thread overview]
Message-ID: <c27ce6d6-ee64-af8b-7cd7-2f263653b5f9@microchip.com> (raw)
In-Reply-To: <1606903025-14197-3-git-send-email-claudiu.beznea@microchip.com>
On 02/12/2020 at 10:57, Claudiu Beznea wrote:
> Due to strobe signal not being propagated from CPU to securam
> the securam needs to be mapped as device or strongly ordered memory
> to work properly. Otherwise, updating to one offset may affect
> the adjacent locations in securam.
>
> Fixes: d4ce5f44d4409 ("ARM: dts: at91: sama5d2: Add securam node")
> Signed-off-by: Claudiu Beznea <claudiu.beznea@microchip.com>
Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
> ---
> arch/arm/boot/dts/sama5d2.dtsi | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/boot/dts/sama5d2.dtsi b/arch/arm/boot/dts/sama5d2.dtsi
> index 2ddc85dff8ce..6d399ac0385d 100644
> --- a/arch/arm/boot/dts/sama5d2.dtsi
> +++ b/arch/arm/boot/dts/sama5d2.dtsi
> @@ -656,6 +656,7 @@
> clocks = <&pmc PMC_TYPE_PERIPHERAL 51>;
> #address-cells = <1>;
> #size-cells = <1>;
> + no-memory-wc;
> ranges = <0 0xf8044000 0x1420>;
> };
>
>
--
Nicolas Ferre
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-12-02 10:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 9:57 [PATCH 0/2] fixes for at91 devices Claudiu Beznea
2020-12-02 9:57 ` Claudiu Beznea
2020-12-02 9:57 ` [PATCH 1/2] ARM: dts: at91: sam9x60ek: remove bypass property Claudiu Beznea
2020-12-02 9:57 ` Claudiu Beznea
2020-12-02 10:27 ` Nicolas Ferre
2020-12-02 10:27 ` Nicolas Ferre
2020-12-02 9:57 ` [PATCH 2/2] ARM: dts: at91: sama5d2: map securam as device Claudiu Beznea
2020-12-02 9:57 ` Claudiu Beznea
2020-12-02 10:27 ` Nicolas Ferre [this message]
2020-12-02 10:27 ` Nicolas Ferre
2020-12-02 12:01 ` [PATCH 0/2] fixes for at91 devices Alexandre Belloni
2020-12-02 12:01 ` Alexandre Belloni
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=c27ce6d6-ee64-af8b-7cd7-2f263653b5f9@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=robh+dt@kernel.org \
--cc=sandeepsheriker.mallikarjun@microchip.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.