From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Marc Kleine-Budde <mkl@pengutronix.de>,
Pankaj Sharma <pankj.sharma@samsung.com>,
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,
davem@davemloft.net, kuba@kernel.org, pankaj.dubey@samsung.com
Subject: Re: [PATCH] can: m_can: add support for bosch mcan version 3.3.0
Date: Thu, 26 Nov 2020 12:21:36 +0100 [thread overview]
Message-ID: <e6f36ce5-1197-d93b-705b-2f7d68761f04@hartkopp.net> (raw)
In-Reply-To: <e7a65c29-d0b0-358f-fc5f-c08944ada4df@pengutronix.de>
On 26.11.20 11:48, Marc Kleine-Budde wrote:
> On 11/26/20 5:51 AM, Pankaj Sharma wrote:
>> 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
>
> BTW: do you have the v3.2 and v3.1 datasheets?
Unfortunately Bosch does not give access to older documents, so I tried
to concentrate all my downloaded versions of public available
information here:
https://github.com/hartkopp/M_CAN-User-Manual-History
PR's with updates are welcome ;-)
Best,
Oliver
ps. @Bosch Semiconductors - Read the README there! I would like to
remove my own collection.
>
> Marc
>
>> 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;
>>
>>
>
>
next prev parent reply other threads:[~2020-11-26 11:21 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
2020-11-26 10:48 ` Marc Kleine-Budde
2020-11-26 11:21 ` Oliver Hartkopp [this message]
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=e6f36ce5-1197-d93b-705b-2f7d68761f04@hartkopp.net \
--to=socketcan@hartkopp.net \
--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=pankj.sharma@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
all inboxes | Powered by JetHome®