From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Thomas.Kopp@microchip.com, geert@linux-m68k.org,
manivannan.sadhasivam@linaro.org, o.rempel@pengutronix.de
Cc: wg@grandegger.com, robh+dt@kernel.org, linux-can@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
dev.kurt@vandijck-laurijssen.be
Subject: Re: [PATCH 2/6] dt-bindings: can: mcp25xxfd: document device tree bindings
Date: Tue, 29 Sep 2020 13:27:33 +0200 [thread overview]
Message-ID: <b26d4c51-7477-3e68-1c16-7b19558d6a57@pengutronix.de> (raw)
In-Reply-To: <DM6PR11MB4283A6A532ED88F7D1058A8BFB320@DM6PR11MB4283.namprd11.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 1325 bytes --]
On 9/29/20 1:25 PM, Thomas.Kopp@microchip.com wrote:
>> So far in that name space there are the mcp2510, mcp2515 and mcp25625.
>> From the
>> SW point of view the 2515 and 25625 are identical while being compatible
>> to the
>> mcp2510 but offer more features. There's a single drver (mcp251x) for
>> these.
>> These chips implement the CAN-2.0 standard.
>>
>> Regarding the mcp2517fd and mcp2518fd, the "fd" in the name references
>> the
>> CAN-FD standard (successor to CAN-2.0).
>>
>> Maybe Thomas Kopp (Cc'ed) from Microchip can say something to this.
>>
>> We can rename the compatible to mcp251xfd to make it more specific.
> I agree that mcp251xfd would be a good fit. We already have (theoretical)
> conflicts for the xx in the namespace e.g. the MCP2542FD which is a
> transceiver without any controller functionality.
>
> Although hard to guarantee I think it's fair to assume that no MCP251xFD
> will be released that is incompatible.
Makes sense to me. Thomas, can you create a patch for this?
regards,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-09-29 12:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 13:38 [PATCH 0/6] Add support for MCP25XXFD SPI-CAN Network driver Manivannan Sadhasivam
2020-09-10 13:38 ` [PATCH 1/6] can: rx-offload: can_rx_offload_add_manual(): add new initialization function Manivannan Sadhasivam
2020-09-10 13:38 ` [PATCH 2/6] dt-bindings: can: mcp25xxfd: document device tree bindings Manivannan Sadhasivam
2020-09-22 19:32 ` Rob Herring
2020-09-29 9:46 ` Geert Uytterhoeven
2020-09-29 10:06 ` Marc Kleine-Budde
2020-09-29 11:25 ` Thomas.Kopp
2020-09-29 11:27 ` Marc Kleine-Budde [this message]
2020-09-10 13:38 ` [PATCH 3/6] can: mcp25xxfd: add regmap infrastructure Manivannan Sadhasivam
2020-09-10 13:38 ` [PATCH 4/6] can: mcp25xxfd: add driver for Microchip MCP25xxFD SPI CAN Manivannan Sadhasivam
2020-09-10 13:38 ` [PATCH 5/6] can: mcp25xxfd: add listen-only mode Manivannan Sadhasivam
2020-09-10 13:38 ` [PATCH 6/6] MAINTAINERS: Add entry for Microchip MCP25XXFD SPI-CAN network driver Manivannan Sadhasivam
2020-09-15 16:19 ` [PATCH 0/6] Add support for MCP25XXFD SPI-CAN Network driver Manivannan Sadhasivam
2020-09-15 17:58 ` Kurt Van Dijck
2020-09-16 4:07 ` Manivannan Sadhasivam
2020-09-16 13:59 ` Marc Kleine-Budde
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=b26d4c51-7477-3e68-1c16-7b19558d6a57@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=Thomas.Kopp@microchip.com \
--cc=dev.kurt@vandijck-laurijssen.be \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=o.rempel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=wg@grandegger.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;
as well as URLs for NNTP newsgroup(s).