From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>,
<linux-kernel@vger.kernel.org>
Cc: Vincent Mailhol <mailhol.vincent@wanadoo.fr>,
Amarula patchwork <linux-amarula@amarulasolutions.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Rob Herring <robh@kernel.org>, <michael@amarulasolutions.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Rob Herring <robh+dt@kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [RESEND RFC PATCH v5 3/5] ARM: dts: stm32: add CAN support on stm32f429
Date: Mon, 9 Jan 2023 15:45:10 +0100 [thread overview]
Message-ID: <b2a88e83-2eac-7b58-4803-b020c0336e34@foss.st.com> (raw)
In-Reply-To: <20230108162554.8375-4-dario.binacchi@amarulasolutions.com>
On 1/8/23 17:25, Dario Binacchi wrote:
> Add support for bxcan (Basic eXtended CAN controller) to STM32F429. The
> chip contains two CAN peripherals, CAN1 the master and CAN2 the slave,
> that share some of the required logic like clock and filters. This means
> that the slave CAN can't be used without the master CAN.
>
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
>
> ---
>
> (no changes since v4)
>
> Changes in v4:
> - Replace the node can@40006400 (compatible "st,stm32f4-bxcan-core")
> with the gcan@40006600 node ("sysnode" compatible). The gcan node
> contains clocks and memory addresses shared by the two can nodes
> of which it's no longer the parent.
> - Add to can nodes the "st,gcan" property (global can memory) which
> references the gcan@40006600 node ("sysnode compatibble).
>
> Changes in v3:
> - Remove 'Dario Binacchi <dariobin@libero.it>' SOB.
> - Add "clocks" to can@0 node.
>
> arch/arm/boot/dts/stm32f429.dtsi | 29 +++++++++++++++++++++++++++++
> 1 file changed, 29 insertions(+)
>
> diff --git a/arch/arm/boot/dts/stm32f429.dtsi b/arch/arm/boot/dts/stm32f429.dtsi
> index c31ceb821231..ce08872109b8 100644
> --- a/arch/arm/boot/dts/stm32f429.dtsi
> +++ b/arch/arm/boot/dts/stm32f429.dtsi
> @@ -362,6 +362,35 @@ i2c3: i2c@40005c00 {
> status = "disabled";
> };
>
> + gcan: gcan@40006600 {
> + compatible = "st,stm32f4-gcan", "syscon";
> + reg = <0x40006600 0x200>;
> + clocks = <&rcc 0 STM32F4_APB1_CLOCK(CAN1)>;
> + };
> +
> + can1: can@40006400 {
> + compatible = "st,stm32f4-bxcan";
> + reg = <0x40006400 0x200>;
> + interrupts = <19>, <20>, <21>, <22>;
> + interrupt-names = "tx", "rx0", "rx1", "sce";
> + resets = <&rcc STM32F4_APB1_RESET(CAN1)>;
> + clocks = <&rcc 0 STM32F4_APB1_CLOCK(CAN1)>;
> + st,can-master;
> + st,gcan = <&gcan>;
> + status = "disabled";
> + };
We try to keep ordering by address. Can you move can1 before gcan ?
Otherwise, it is ok for me.
> +
> + can2: can@40006800 {
> + compatible = "st,stm32f4-bxcan";
> + reg = <0x40006800 0x200>;
> + interrupts = <63>, <64>, <65>, <66>;
> + interrupt-names = "tx", "rx0", "rx1", "sce";
> + resets = <&rcc STM32F4_APB1_RESET(CAN2)>;
> + clocks = <&rcc 0 STM32F4_APB1_CLOCK(CAN2)>;
> + st,gcan = <&gcan>;
> + status = "disabled";
> + };
> +
> dac: dac@40007400 {
> compatible = "st,stm32f4-dac-core";
> reg = <0x40007400 0x400>;
next prev parent reply other threads:[~2023-01-09 14:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 16:25 [RESEND RFC PATCH v5 0/5] can: bxcan: add support for ST bxCAN controller Dario Binacchi
2023-01-08 16:25 ` [RESEND RFC PATCH v5 1/5] dt-bindings: arm: stm32: add compatible for syscon gcan node Dario Binacchi
2023-01-08 16:25 ` [RESEND RFC PATCH v5 2/5] dt-bindings: net: can: add STM32 bxcan DT bindings Dario Binacchi
2023-01-08 16:25 ` [RESEND RFC PATCH v5 3/5] ARM: dts: stm32: add CAN support on stm32f429 Dario Binacchi
2023-01-09 14:45 ` Alexandre TORGUE [this message]
2023-01-08 16:25 ` [RESEND RFC PATCH v5 4/5] ARM: dts: stm32: add pin map for CAN controller on stm32f4 Dario Binacchi
2023-01-08 16:25 ` [RESEND RFC PATCH v5 5/5] can: bxcan: add support for ST bxCAN controller Dario Binacchi
-- strict thread matches above, loose matches on Subject: below --
2022-11-13 18:13 [RESEND RFC PATCH v5 0/5] " Dario Binacchi
2022-11-13 18:13 ` [RESEND RFC PATCH v5 3/5] ARM: dts: stm32: add CAN support on stm32f429 Dario Binacchi
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=b2a88e83-2eac-7b58-4803-b020c0336e34@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mcoquelin.stm32@gmail.com \
--cc=michael@amarulasolutions.com \
--cc=mkl@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=robh@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®