From: <Claudiu.Beznea@microchip.com>
To: <Kavyasree.Kotagiri@microchip.com>,
<alexandre.belloni@bootlin.com>,
<krzysztof.kozlowski+dt@linaro.org>, <robh+dt@kernel.org>,
<Nicolas.Ferre@microchip.com>
Cc: <arnd@arndb.de>, <soc@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<UNGLinuxDriver@microchip.com>
Subject: Re: [PATCH] ARM: dts: lan966x: Add mcan1 node.
Date: Mon, 4 Jul 2022 06:48:13 +0000 [thread overview]
Message-ID: <4c17f88a-7e82-4734-1001-0bd5da218654@microchip.com> (raw)
In-Reply-To: <20220627110552.26315-1-kavyasree.kotagiri@microchip.com>
On 27.06.2022 14:05, Kavyasree Kotagiri wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> Add the mcan1 node. By default, keep it disabled.
>
> Signed-off-by: Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>
Applied to at91-dt, thanks!
> ---
> arch/arm/boot/dts/lan966x.dtsi | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/arch/arm/boot/dts/lan966x.dtsi b/arch/arm/boot/dts/lan966x.dtsi
> index 3cb02fffe716..25cfa89dde7b 100644
> --- a/arch/arm/boot/dts/lan966x.dtsi
> +++ b/arch/arm/boot/dts/lan966x.dtsi
> @@ -473,6 +473,21 @@
> status = "disabled";
> };
>
> + can1: can@e0820000 {
> + compatible = "bosch,m_can";
> + reg = <0xe0820000 0xfc>, <0x00100000 0x8000>;
> + reg-names = "m_can", "message_ram";
> + interrupts = <GIC_SPI 74 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 75 IRQ_TYPE_LEVEL_HIGH>;
> + interrupt-names = "int0", "int1";
> + clocks = <&clks GCK_ID_MCAN1>, <&clks GCK_ID_MCAN1>;
> + clock-names = "hclk", "cclk";
> + assigned-clocks = <&clks GCK_ID_MCAN1>;
> + assigned-clock-rates = <40000000>;
> + bosch,mram-cfg = <0x4000 0 0 64 0 0 32 32>;
> + status = "disabled";
> + };
> +
> reset: reset-controller@e200400c {
> compatible = "microchip,lan966x-switch-reset";
> reg = <0xe200400c 0x4>;
> --
> 2.17.1
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-07-04 6:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 11:05 [PATCH] ARM: dts: lan966x: Add mcan1 node Kavyasree Kotagiri
2022-07-01 8:16 ` Nicolas Ferre
2022-07-04 6:48 ` Claudiu.Beznea [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=4c17f88a-7e82-4734-1001-0bd5da218654@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Kavyasree.Kotagiri@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=soc@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