From: Ciprian Marian Costea <ciprianmarian.costea@oss.nxp.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
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>, Frank Li <Frank.Li@nxp.com>
Subject: Re: [PATCH v2 1/3] dt-bindings: can: fsl,flexcan: add S32G2/S32G3 SoC support
Date: Tue, 26 Nov 2024 17:21:14 +0200 [thread overview]
Message-ID: <e8d11c7f-0bf5-44cd-bb2d-a7e454905e53@oss.nxp.com> (raw)
In-Reply-To: <20241126-conscious-keen-cricket-c603ff-mkl@pengutronix.de>
On 11/26/2024 5:19 PM, Marc Kleine-Budde wrote:
> On 26.11.2024 16:18:41, Marc Kleine-Budde wrote:
>> On 26.11.2024 17:15:10, Ciprian Marian Costea wrote:
>>>>>>>> + interrupt-names:
>>>>>>>> + items:
>>>>>>>> + - const: mb_0-7
>>>>
>>>> I was wondering if it makes sense to have an interrupt name not
>>>> mentioning the exact mailbox numbers, so that the same interrupt name
>>>> can be used for a different IP core, too. On the coldfire SoC the 1st
>>>> IRQ handles mailboxes 0...15.
>>>>
>>>
>>> I am ok with proposing a more generic name for mailboxes in order to
>>> increase reusability among FlexCAN enabled SoCs.
>>> Further specific mailbox numbers could be mentioned in the actual
>>> S32G2/S32G3 dtsi flexcan node.
>>>
>>> One proposal could be:
>>> - mb-1: First Range of Mailboxes
>>> - mb-2: Second Range of Mailboxes
>>>
>>> Let me know if you agree to update as proposed in V3.
>>
>> Looks good to me!
>
> Or maybe start with "0", that makes it a bit easier to construct the
> names of the IRQ-names in a for loop.
>
> regards,
> Marc
>
That makes sense. Thanks for the suggestion.
Best Regards,
Ciprian
next prev parent reply other threads:[~2024-11-26 15:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 16:30 [PATCH v2 0/3] add FlexCAN support for S32G2/S32G3 SoCs Ciprian Costea
2024-11-25 16:31 ` [PATCH v2 1/3] dt-bindings: can: fsl,flexcan: add S32G2/S32G3 SoC support Ciprian Costea
2024-11-26 7:19 ` Krzysztof Kozlowski
2024-11-26 7:47 ` Ciprian Marian Costea
2024-11-26 10:59 ` Marc Kleine-Budde
2024-11-26 13:48 ` Ciprian Marian Costea
2024-11-26 15:02 ` Marc Kleine-Budde
2024-11-26 15:15 ` Ciprian Marian Costea
2024-11-26 15:18 ` Marc Kleine-Budde
2024-11-26 15:19 ` Marc Kleine-Budde
2024-11-26 15:21 ` Ciprian Marian Costea [this message]
2024-11-27 7:23 ` Marc Kleine-Budde
2024-11-27 7:37 ` Ciprian Marian Costea
2024-11-25 16:31 ` [PATCH v2 2/3] can: flexcan: Add quirk to handle separate interrupt lines for mailboxes Ciprian Costea
2024-11-26 2:59 ` Vincent Mailhol
2024-11-25 16:31 ` [PATCH v2 3/3] can: flexcan: add NXP S32G2/S32G3 SoC support 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=e8d11c7f-0bf5-44cd-bb2d-a7e454905e53@oss.nxp.com \
--to=ciprianmarian.costea@oss.nxp.com \
--cc=Frank.Li@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=krzk@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
all inboxes | Powered by JetHome®