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 14:57:22 +0200 [thread overview]
Message-ID: <570F93B2.1010804@pengutronix.de> (raw)
In-Reply-To: <KL1PR06MB10312DC099D9EE3A19B6B872C3970@KL1PR06MB1031.apcprd06.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 871 bytes --]
On 04/14/2016 02:46 PM, Ramesh Shanmugasundaram wrote:
>> Thanks for your thoughts I'll use algorithm 2 then.
>
> If not done already, is it worth comparing the algorithm for
> dbitrates (fd case) too as same code is used?
The reworked algorithm will not pick worse values than the original one.
However, I'll update the tool for dbitrates. Are there any common
dbitrates? The array if common bitrates is:
> static unsigned int common_bitrates[] = {
> 1000000,
> 800000,
> 500000,
> 250000,
> 125000,
> 100000,
> 50000,
> 20000,
> 10000,
> };
regards,
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 12:57 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 [this message]
2016-04-14 13:05 ` Ramesh Shanmugasundaram
2016-04-14 14:06 ` Marc Kleine-Budde
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=570F93B2.1010804@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.