From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Ramesh Shanmugasundaram <ramesh.shanmugasundaram@bp.renesas.com>,
linux-can <linux-can@vger.kernel.org>
Subject: Re: bit-timing and sample point
Date: Thu, 14 Apr 2016 16:06:22 +0200 [thread overview]
Message-ID: <570FA3DE.9030001@pengutronix.de> (raw)
In-Reply-To: <KL1PR06MB1031E7E5F2414AF6C81030A4C3970@KL1PR06MB1031.apcprd06.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 929 bytes --]
On 04/14/2016 03:05 PM, Ramesh Shanmugasundaram wrote:
>> Are there any common dbitrates? The array if common bitrates is:
>
> Not sure. I read in one of the NXP white paper 2 & 5Mbps are common
> data bitrates. I have tested 2Mbps only (transceiver capability). May
> be we can start with 2, 5 & 8Mbps. The tool already allows to print
> values for a specific bitrate. So we are covered.
12 MBit/s seems to be the max.
> static unsigned int common_data_bitrates[] = {
> 12000000,
> 10000000,
> 8000000,
> 5000000,
> 4000000,
> 2000000,
> 1000000,
> };
Can you give the the typical refclocks for the rcar canfd?
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2016-04-14 14:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 10:32 bit-timing and sample point Marc Kleine-Budde
2016-04-14 10:26 ` Kurt Van Dijck
2016-04-14 10:47 ` Marc Kleine-Budde
2016-04-14 12:19 ` Kurt Van Dijck
2016-04-14 12:32 ` Marc Kleine-Budde
2016-04-14 12:46 ` Ramesh Shanmugasundaram
2016-04-14 12:57 ` Marc Kleine-Budde
2016-04-14 13:05 ` Ramesh Shanmugasundaram
2016-04-14 14:06 ` Marc Kleine-Budde [this message]
2016-04-14 14:13 ` Ramesh Shanmugasundaram
2016-06-17 9:46 ` Ramesh Shanmugasundaram
2016-06-17 9:59 ` Marc Kleine-Budde
2016-06-17 10:02 ` Ramesh Shanmugasundaram
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=570FA3DE.9030001@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=ramesh.shanmugasundaram@bp.renesas.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