From: Ciprian Costea <ciprianmarian.costea@oss.nxp.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>,
Vincent Mailhol <mailhol.vincent@wanadoo.fr>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-can@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, NXP Linux Team <s32@nxp.com>,
Christophe Lizzi <clizzi@redhat.com>,
Alberto Ruiz <aruizrui@redhat.com>,
Enric Balletbo <eballetb@redhat.com>,
Ciprian Marian Costea <ciprianmarian.costea@oss.nxp.com>
Subject: [PATCH v3 0/3] add FlexCAN support for S32G2/S32G3 SoCs
Date: Tue, 19 Nov 2024 10:01:41 +0200 [thread overview]
Message-ID: <20241119080144.4173712-1-ciprianmarian.costea@oss.nxp.com> (raw)
From: Ciprian Marian Costea <ciprianmarian.costea@oss.nxp.com>
S32G2 and S32G3 SoCs share the FlexCAN module with i.MX SoCs, with some
hardware integration particularities.
Main difference covered by this patchset relates to interrupt management.
On S32G2/S32G3 SoC, there are separate interrupts for state change, bus
errors, MBs 0-7 and MBs 8-127 respectively.
The intent of this patchset is to be upstream'ed on the official Linux
repo [0].
Since S32G2/S32G3 SoCs share the FlexCAN controller with I.MX platforms,
we find value in an allignment on Linux Factory tree [1]. Hence, we are
looking forward to integrate any feedback which you have based on your
expertise on this proposed patchset, before finally submitting upstream
for review.
[0] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
[1] https://bitbucket.sw.nxp.com/projects/LFAC/repos/linux-nxp/browse
Changes in V3:
- Refactored FlexCan binding documentation changes
- Rephrased/Clarified some commit messages
Changes in V2:
- Fixed several issues in FlexCan binding documentation
Ciprian Marian Costea (3):
dt-bindings: can: fsl,flexcan: add S32G2/S32G3 SoC support
can: flexcan: add NXP S32G2/S32G3 SoC support
can: flexcan: handle S32G2/S32G3 separate interrupt lines
.../bindings/net/can/fsl,flexcan.yaml | 25 +++++++++++++--
drivers/net/can/flexcan/flexcan-core.c | 31 +++++++++++++++++++
drivers/net/can/flexcan/flexcan.h | 3 ++
3 files changed, 56 insertions(+), 3 deletions(-)
--
2.45.2
next reply other threads:[~2024-11-19 8:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 8:01 Ciprian Costea [this message]
2024-11-19 8:01 ` [PATCH v3 1/3] dt-bindings: can: fsl,flexcan: add S32G2/S32G3 SoC support Ciprian Costea
2024-11-19 8:01 ` [PATCH v3 2/3] can: flexcan: add NXP " Ciprian Costea
2024-11-19 8:07 ` [PATCH v3 0/3] add FlexCAN support for S32G2/S32G3 SoCs Ciprian Marian Costea
-- strict thread matches above, loose matches on Subject: below --
2024-11-29 14:25 Ciprian 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=20241119080144.4173712-1-ciprianmarian.costea@oss.nxp.com \
--to=ciprianmarian.costea@oss.nxp.com \
--cc=andrew+netdev@lunn.ch \
--cc=aruizrui@redhat.com \
--cc=clizzi@redhat.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=eballetb@redhat.com \
--cc=edumazet@google.com \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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