From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Brian Silverman <bsilver16384@gmail.com>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
open list <linux-kernel@vger.kernel.org>,
"open list:CAN NETWORK DRIVERS" <linux-can@vger.kernel.org>,
"open list:TEGRA ARCHITECTURE SUPPORT"
<linux-tegra@vger.kernel.org>
Subject: Re: [RFC PATCH] can: m_can: Add driver for M_CAN hardware in NVIDIA devices
Date: Sun, 9 Jan 2022 00:25:03 +0100 [thread overview]
Message-ID: <20220108232503.ecwf7f4uuo7s7eni@pengutronix.de> (raw)
In-Reply-To: <20220106002514.24589-1-brian.silverman@bluerivertech.com>
[-- Attachment #1: Type: text/plain, Size: 2163 bytes --]
On 05.01.2022 16:25:09, Brian Silverman wrote:
> It's a M_TTCAN with some NVIDIA-specific glue logic and clocks. The
> existing m_can driver works with it after handling the glue logic.
>
> The code is a combination of pieces from m_can_platform and NVIDIA's
> driver [1].
>
> [1] https://github.com/hartkopp/nvidia-t18x-can/blob/master/r32.2.1/nvidia/drivers/net/can/mttcan/hal/m_ttcan.c
>
> Signed-off-by: Brian Silverman <brian.silverman@bluerivertech.com>
Thanks for your patch.
> ---
> I ran into bugs with the error handling in NVIDIA's m_ttcan driver, so I
> switched to m_can which has been much better. I'm looking for feedback
> on whether I should ensure rebasing hasn't broken anything, write up DT
> documentation, and submit this patch for real. The driver works great,
> but I've got some questions about submitting it.
>
> question: This has liberal copying of GPL code from NVIDIA's
> non-upstreamed m_ttcan driver. Is that OK?
The header in the driver says it's GPLv2:
| https://github.com/hartkopp/nvidia-t18x-can/blob/master/r32.2.1/nvidia/drivers/net/can/mttcan/hal/m_ttcan.c#L5
So it's OK. You should copy the original copyright notice to your glue
driver, though.
> corollary: I don't know what any of this glue logic does. I do know the
> device doesn't work without it. I can't find any documentation of what
> these addresses do.
hmmm ok
> question: There is some duplication between this and m_can_platform. It
> doesn't seem too bad to me, but is this the preferred way to do it or is
> there another alternative?
You might merge this driver to the generic platform driver.
> question: Do new DT bindings need to be in the YAML format, or is the
> .txt one OK?
YAML
Please fix the checkpatch warning found by:
| ./scripts/checkpatch.pl --file drivers/net/can/m_can/m_can_tegra.c
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: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-01-08 23:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 0:25 [RFC PATCH] can: m_can: Add driver for M_CAN hardware in NVIDIA devices Brian Silverman
2022-01-08 23:25 ` Marc Kleine-Budde [this message]
2022-04-06 15:18 ` Thierry Reding
2022-04-07 13:01 ` 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=20220108232503.ecwf7f4uuo7s7eni@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=bsilver16384@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.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