From: Wolfgang Grandegger <wg@grandegger.com> To: Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com> Cc: socketcan-core@lists.berlios.de, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: About bittiming calculation result Date: Tue, 08 Feb 2011 08:57:14 +0100 [thread overview] Message-ID: <4D50F75A.5040700@grandegger.com> (raw) In-Reply-To: <93C12206407640199DCDD3A89A333F13@hacdom.okisemi.com> Hi Tomoya, On 02/08/2011 02:27 AM, Tomoya MORINAGA wrote: > On Tuesday, February 08, 2011 12:53 AM, Wolfgang Grandegger wrote: > >> BTW, it's always possible to specify optimized bit-timing >> parameters directly, e.g. the following seem better: >> >> 800000 60 12 4 4 4 3 793650 0.8% 80.0% 81.0% 1.2% >> >> You could set these with: >> >> $ ip link set can0 type can \ >> tq 60 prop-seg 12 phase-seg1 4 phase-seg2 4 sjw 4 > > I can confirm 800K comms works well using the above. Cool, I got these magic values from a CAN hardware expert. > I wish Can-core could calculate like above. Me too! I also got some indication on how to improve our algorithm in case the bit-rate does not match. Hope to find some time soon to work on this issue. >>> seg1/seg2/sjw/prop_seg must be more than 1 ? > BTW, according to EG20T PCH data sheet, > CAN bit-timing parameters(BRP, Prop_Seg, Phase_Seg1, Phase_Seg2, SJW) must not be set 0. OK, then please provide a patch setting tseg1_min to 2. Wolfgang.
WARNING: multiple messages have this Message-ID (diff)
From: Wolfgang Grandegger <wg-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org> To: Tomoya MORINAGA <tomoya-linux-ECg8zkTtlr0C6LszWs/t0g@public.gmane.org> Cc: socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org, netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Subject: Re: About bittiming calculation result Date: Tue, 08 Feb 2011 08:57:14 +0100 [thread overview] Message-ID: <4D50F75A.5040700@grandegger.com> (raw) In-Reply-To: <93C12206407640199DCDD3A89A333F13-c0cKtqp5df7I9507bXv2FdBPR1lH4CV8@public.gmane.org> Hi Tomoya, On 02/08/2011 02:27 AM, Tomoya MORINAGA wrote: > On Tuesday, February 08, 2011 12:53 AM, Wolfgang Grandegger wrote: > >> BTW, it's always possible to specify optimized bit-timing >> parameters directly, e.g. the following seem better: >> >> 800000 60 12 4 4 4 3 793650 0.8% 80.0% 81.0% 1.2% >> >> You could set these with: >> >> $ ip link set can0 type can \ >> tq 60 prop-seg 12 phase-seg1 4 phase-seg2 4 sjw 4 > > I can confirm 800K comms works well using the above. Cool, I got these magic values from a CAN hardware expert. > I wish Can-core could calculate like above. Me too! I also got some indication on how to improve our algorithm in case the bit-rate does not match. Hope to find some time soon to work on this issue. >>> seg1/seg2/sjw/prop_seg must be more than 1 ? > BTW, according to EG20T PCH data sheet, > CAN bit-timing parameters(BRP, Prop_Seg, Phase_Seg1, Phase_Seg2, SJW) must not be set 0. OK, then please provide a patch setting tseg1_min to 2. Wolfgang.
next prev parent reply other threads:[~2011-02-08 7:55 UTC|newest] Thread overview: 101+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-02-04 12:22 [PATCH 00/20] world-writable files in sysfs and debugfs Vasiliy Kulikov 2011-02-04 12:22 ` Vasiliy Kulikov 2011-02-04 12:22 ` Vasiliy Kulikov 2011-02-04 12:22 ` Vasiliy Kulikov 2011-02-04 12:23 ` [PATCH 01/20] mach-omap2: mux: world-writable debugfs files Vasiliy Kulikov 2011-02-04 12:23 ` Vasiliy Kulikov 2011-02-04 20:09 ` Tony Lindgren 2011-02-04 20:09 ` Tony Lindgren 2011-02-04 12:23 ` [PATCH 02/20] mach-omap2: pm: world-writable debugfs timer files Vasiliy Kulikov 2011-02-04 12:23 ` Vasiliy Kulikov 2011-02-04 20:10 ` Tony Lindgren 2011-02-04 20:10 ` Tony Lindgren 2011-02-04 22:53 ` Kevin Hilman 2011-02-04 22:53 ` Kevin Hilman 2011-02-04 12:23 ` [PATCH 03/20] mach-omap2: smartreflex: world-writable debugfs voltage files Vasiliy Kulikov 2011-02-04 12:23 ` Vasiliy Kulikov 2011-02-04 20:10 ` Tony Lindgren 2011-02-04 20:10 ` Tony Lindgren 2011-02-04 22:54 ` Kevin Hilman 2011-02-04 22:54 ` Kevin Hilman 2011-02-07 5:33 ` Menon, Nishanth 2011-02-07 5:33 ` Menon, Nishanth 2011-02-04 12:23 ` [PATCH 04/20] mach-ux500: mbox-db5500: world-writable sysfs fifo file Vasiliy Kulikov 2011-02-04 12:23 ` Vasiliy Kulikov 2011-02-04 12:23 ` [PATCH 05/20] leds: lp5521: world-writable sysfs engine* files Vasiliy Kulikov 2011-02-04 12:23 ` [PATCH 06/20] leds: lp5523: world-writable engine* sysfs files Vasiliy Kulikov 2011-02-04 12:23 ` [PATCH 07/20] video: sn9c102: world-wirtable " Vasiliy Kulikov 2011-02-04 15:29 ` Mauro Carvalho Chehab 2011-02-04 20:28 ` Luca Risolia 2011-02-04 12:23 ` [PATCH 08/20] mfd: ab3100: world-writable debugfs *_priv files Vasiliy Kulikov 2011-02-04 12:23 ` Vasiliy Kulikov 2011-02-18 17:01 ` Vasiliy Kulikov 2011-02-04 12:23 ` [PATCH 09/20] mfd: ab3500: world-writable debugfs register-* files Vasiliy Kulikov 2011-02-04 12:23 ` Vasiliy Kulikov 2011-02-04 12:23 ` [PATCH 10/20] mfd: ab8500: " Vasiliy Kulikov 2011-02-04 12:23 ` Vasiliy Kulikov 2011-02-04 12:23 ` [PATCH 11/20] misc: ep93xx_pwm: world-writable sysfs files Vasiliy Kulikov 2011-02-04 12:23 ` [PATCH 12/20] net: can: at91_can: " Vasiliy Kulikov 2011-02-04 12:42 ` Kurt Van Dijck 2011-02-04 12:42 ` Kurt Van Dijck 2011-02-04 21:06 ` David Miller 2011-02-04 21:06 ` David Miller 2011-02-07 11:38 ` About bittiming calculation result Tomoya MORINAGA 2011-02-07 12:00 ` Wolfgang Grandegger 2011-02-07 12:00 ` Wolfgang Grandegger 2011-02-07 15:52 ` Wolfgang Grandegger 2011-02-07 15:52 ` Wolfgang Grandegger 2011-02-08 1:27 ` Tomoya MORINAGA 2011-02-08 1:27 ` Tomoya MORINAGA 2011-02-08 7:57 ` Wolfgang Grandegger [this message] 2011-02-08 7:57 ` Wolfgang Grandegger 2011-02-08 1:09 ` Tomoya MORINAGA 2011-02-08 1:09 ` Tomoya MORINAGA 2011-02-08 3:29 ` Bhupesh SHARMA 2011-02-08 3:29 ` Bhupesh SHARMA 2011-02-08 4:11 ` Tomoya MORINAGA 2011-02-08 4:11 ` Tomoya MORINAGA 2011-02-04 12:23 ` [PATCH 13/20] net: can: janz-ican3: world-writable sysfs termination file Vasiliy Kulikov 2011-02-04 21:06 ` David Miller 2011-02-04 21:06 ` David Miller 2011-02-04 12:23 ` [PATCH 14/20] platform: x86: acer-wmi: world-writable sysfs threeg file Vasiliy Kulikov 2011-02-04 12:23 ` [PATCH 15/20] platform: x86: asus_acpi: world-writable procfs files Vasiliy Kulikov 2011-02-04 12:23 ` Vasiliy Kulikov 2011-02-04 12:53 ` Corentin Chary 2011-02-04 12:24 ` [PATCH 16/20] platform: x86: tc1100-wmi: world-writable sysfs wireless and jogdial files Vasiliy Kulikov 2011-02-04 12:24 ` [PATCH 17/20] rtc: rtc-ds1511: world-writable sysfs nvram file Vasiliy Kulikov 2011-02-04 12:24 ` [PATCH 18/20] scsi: aic94xx: world-writable sysfs update_bios file Vasiliy Kulikov 2011-02-04 12:24 ` [PATCH 19/20] scsi: iscsi: world-writable sysfs priv_sess file Vasiliy Kulikov 2011-03-13 8:28 ` Mike Christie 2011-03-13 8:28 ` Mike Christie 2011-02-04 12:24 ` [PATCH 20/20] fs: ubifs: world-writable debugfs dump_* files Vasiliy Kulikov 2011-02-04 12:24 ` Vasiliy Kulikov 2011-02-06 15:16 ` Artem Bityutskiy 2011-02-06 15:16 ` Artem Bityutskiy 2011-02-04 13:11 ` [rtc-linux] [PATCH 00/20] world-writable files in sysfs and debugfs Linus Walleij 2011-02-04 13:11 ` Linus Walleij 2011-02-04 13:11 ` Linus Walleij 2011-02-04 13:11 ` Linus Walleij 2011-02-21 11:42 ` Samuel Ortiz 2011-03-12 20:23 ` Vasiliy Kulikov 2011-03-12 20:23 ` Vasiliy Kulikov 2011-03-12 20:23 ` Vasiliy Kulikov 2011-03-14 22:18 ` [Security] " Andrew Morton 2011-03-14 22:18 ` Andrew Morton 2011-03-15 2:26 ` James Bottomley 2011-03-15 2:26 ` James Bottomley 2011-03-15 3:09 ` [Security] " Greg KH 2011-03-15 3:09 ` Greg KH 2011-03-15 11:50 ` James Bottomley 2011-03-15 11:50 ` James Bottomley 2011-03-15 14:18 ` Greg KH 2011-03-15 14:18 ` Greg KH 2011-03-15 14:25 ` James Bottomley 2011-03-15 14:25 ` James Bottomley 2011-03-15 16:08 ` Vasiliy Kulikov 2011-03-15 16:08 ` Vasiliy Kulikov 2011-03-15 16:32 ` James Bottomley 2011-03-15 16:32 ` James Bottomley 2011-03-15 16:32 ` James Bottomley 2011-03-12 20:23 ` Vasiliy Kulikov 2011-03-12 20:23 ` Vasiliy Kulikov
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=4D50F75A.5040700@grandegger.com \ --to=wg@grandegger.com \ --cc=linux-kernel@vger.kernel.org \ --cc=netdev@vger.kernel.org \ --cc=socketcan-core@lists.berlios.de \ --cc=tomoya-linux@dsn.okisemi.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: linkBe 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.