From: Ciprian Marian Costea <ciprianmarian.costea@oss.nxp.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Vincent Mailhol <mailhol.vincent@wanadoo.fr>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-can@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, NXP S32 Linux <s32@nxp.com>,
imx@lists.linux.dev, Christophe Lizzi <clizzi@redhat.com>,
Alberto Ruiz <aruizrui@redhat.com>,
Enric Balletbo <eballetb@redhat.com>
Subject: Re: [PATCH v4 3/3] can: flexcan: add NXP S32G2/S32G3 SoC support
Date: Wed, 4 Dec 2024 13:38:51 +0200 [thread overview]
Message-ID: <1147e8d9-b6e1-4290-9cfa-888d93f185e9@oss.nxp.com> (raw)
In-Reply-To: <20241204-chipmunk-of-unmatched-research-e89301-mkl@pengutronix.de>
On 12/4/2024 10:05 AM, Marc Kleine-Budde wrote:
> On 04.12.2024 09:49:15, Ciprian Costea wrote:
>> From: Ciprian Marian Costea <ciprianmarian.costea@oss.nxp.com>
>>
>> Add device type data for S32G2/S32G3 SoC.
>>
>> FlexCAN module from S32G2/S32G3 is similar with i.MX SoCs, but interrupt
>> management is different.
>>
>> On S32G2/S32G3 SoC, there are separate interrupts for state change, bus
>> errors, Mailboxes 0-7 and Mailboxes 8-127 respectively.
>> In order to handle this FlexCAN hardware particularity, first reuse the
>> 'FLEXCAN_QUIRK_NR_IRQ_3' quirk provided by mcf5441x's irq handling
>> support. Secondly, use the newly introduced
>> 'FLEXCAN_QUIRK_SECONDARY_MB_IRQ' quirk which handles the case where two
>> separate mailbox ranges are controlled by independent hardware interrupt
>> lines.
>>
>> Signed-off-by: Ciprian Marian Costea <ciprianmarian.costea@oss.nxp.com>
>> ---
>
> Looks good to me!
>
> Unrelated to this patch, but I want to extend the "FLEXCAN hardware
> feature flags" table in "flexcan.h". Can you provide the needed
> information?
>
Hello Marc,
I would say the following S32G related information could be added:
>> /* FLEXCAN hardware feature flags
>> *
>> * Below is some version info we got:
>> * SOC Version IP-Version Glitch- [TR]WRN_INT IRQ Err Memory err RTR rece- FD Mode MB
>> * Filter? connected? Passive detection ption in MB Supported?
>> * MCF5441X FlexCAN2 ? no yes no no no no 16
>> * MX25 FlexCAN2 03.00.00.00 no no no no no no 64
>> * MX28 FlexCAN2 03.00.04.00 yes yes no no no no 64
>> * MX35 FlexCAN2 03.00.00.00 no no no no no no 64
>> * MX53 FlexCAN2 03.00.00.00 yes no no no no no 64
>> * MX6s FlexCAN3 10.00.12.00 yes yes no no yes no 64
>> * MX8QM FlexCAN3 03.00.23.00 yes yes no no yes yes 64
>> * MX8MP FlexCAN3 03.00.17.01 yes yes no yes yes yes 64
>> * VF610 FlexCAN3 ? no yes no yes yes? no 64
>> * LS1021A FlexCAN2 03.00.04.00 no yes no no yes no 64
>> * LX2160A FlexCAN3 03.00.23.00 no yes no yes yes yes 64
* S32G2/S32G3 FlexCAN3 03.00.39.00 no yes no
yes yes yes 128
>> *
>> * Some SOCs do not have the RX_WARN & TX_WARN interrupt line connected.
>> */
>
> regards,
> Marc
>
Would you like me to send another version of this patchset with above
information included ?
Best Regards,
Ciprian
next prev parent reply other threads:[~2024-12-04 11:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 7:49 [PATCH v4 0/3] add FlexCAN support for S32G2/S32G3 SoCs Ciprian Costea
2024-12-04 7:49 ` [PATCH v4 1/3] dt-bindings: can: fsl,flexcan: add S32G2/S32G3 SoC support Ciprian Costea
2024-12-04 17:57 ` Conor Dooley
2025-02-06 12:47 ` Marc Kleine-Budde
2024-12-04 7:49 ` [PATCH v4 2/3] can: flexcan: Add quirk to handle separate interrupt lines for mailboxes Ciprian Costea
2024-12-04 7:49 ` [PATCH v4 3/3] can: flexcan: add NXP S32G2/S32G3 SoC support Ciprian Costea
2024-12-04 8:05 ` Marc Kleine-Budde
2024-12-04 11:38 ` Ciprian Marian Costea [this message]
2024-12-04 11:48 ` Marc Kleine-Budde
2025-02-03 13:53 ` Ciprian Marian Costea
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=1147e8d9-b6e1-4290-9cfa-888d93f185e9@oss.nxp.com \
--to=ciprianmarian.costea@oss.nxp.com \
--cc=aruizrui@redhat.com \
--cc=clizzi@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eballetb@redhat.com \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mkl@pengutronix.de \
--cc=robh@kernel.org \
--cc=s32@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox