From: Pankaj Sharma <pankj.sharma@samsung.com>
To: linux-can@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: sriram.dash@samsung.com, dmurphy@ti.com, wg@grandegger.com,
mkl@pengutronix.de, davem@davemloft.net, kuba@kernel.org,
pankaj.dubey@samsung.com,
Pankaj Sharma <pankj.sharma@samsung.com>
Subject: [PATCH] can: m_can: add support for bosch mcan version 3.3.0
Date: Thu, 26 Nov 2020 10:21:42 +0530 [thread overview]
Message-ID: <1606366302-5520-1-git-send-email-pankj.sharma@samsung.com> (raw)
In-Reply-To: CGME20201126045221epcas5p46f00cd452b8023262f5556e6f4567352@epcas5p4.samsung.com
Add support for mcan bit timing and control mode according to bosch mcan IP
version 3.3.0
The mcan version read from the Core Release field of CREL register would be
33. Accordingly the properties are to be set for mcan v3.3.0
Signed-off-by: Pankaj Sharma <pankj.sharma@samsung.com>
---
Depends on:
https://marc.info/?l=linux-can&m=160624495218700&w=2
drivers/net/can/m_can/m_can.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/net/can/m_can/m_can.c b/drivers/net/can/m_can/m_can.c
index 86bbbfa..7652175 100644
--- a/drivers/net/can/m_can/m_can.c
+++ b/drivers/net/can/m_can/m_can.c
@@ -1385,6 +1385,8 @@ static int m_can_dev_setup(struct m_can_classdev *m_can_dev)
&m_can_data_bittiming_const_31X;
break;
case 32:
+ case 33:
+ /* Support both MCAN version v3.2.x and v3.3.0 */
m_can_dev->can.bittiming_const = m_can_dev->bit_timing ?
m_can_dev->bit_timing : &m_can_bittiming_const_31X;
--
2.7.4
next parent reply other threads:[~2020-11-26 10:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20201126045221epcas5p46f00cd452b8023262f5556e6f4567352@epcas5p4.samsung.com>
2020-11-26 4:51 ` Pankaj Sharma [this message]
2020-11-26 10:48 ` [PATCH] can: m_can: add support for bosch mcan version 3.3.0 Marc Kleine-Budde
2020-11-26 11:21 ` Oliver Hartkopp
2020-11-26 12:21 ` pankj.sharma
2020-11-26 10:51 ` 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=1606366302-5520-1-git-send-email-pankj.sharma@samsung.com \
--to=pankj.sharma@samsung.com \
--cc=davem@davemloft.net \
--cc=dmurphy@ti.com \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pankaj.dubey@samsung.com \
--cc=sriram.dash@samsung.com \
--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).