linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Whitmore <arigead@gmail.com>
To: linux-can@vger.kernel.org
Subject: baudrate detection
Date: Thu, 12 Dec 2013 18:40:13 +0000	[thread overview]
Message-ID: <20131212184012.GA18112@griso.site> (raw)

Hi linux-can,

I'm coming from the embedded micro controller end of using CAN and have created
my own CAN Network nodes. Now I'm working with a MCP2515 connected to the
Raspberry Pi, so looking at the Linux Kernel.

On my existing nodes the Initialisation of the CAN device the node either knows
the baudrate to setup or it does not. A node that is a fixed node on the
network knows the baudrate of the network, although this can be changed on the
fly. Other devices are not a fixed part of the network and are connected
dynamically to the network for testing or management purposes. These nodes
don't know the baudrate of the network so automatically detect it. When they
detect the baudrate they then connect and inform the higher application code
that the network is connected, so they can proceed.

I was thinking of adding this auto baudrate detection functionality to the
RaspberryPi but being new to Linux development I'm struggling with whether
this functionality should be in Kernel or User Space. I was initially thinking
User Space but given that numerous applications can be using the CAN Network
you really want to centralise this functionality. That possibly means Kernel
Space?

So before I start to do something I thought I'd ask the experts. Does
automatic baudrate detection belong in Kernel Space or out in Userland? Maybe
it's already in the existing Kernel I've just missed it.

JW

             reply	other threads:[~2013-12-12 18:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-12 18:40 John Whitmore [this message]
2013-12-14 13:29 ` baudrate detection 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=20131212184012.GA18112@griso.site \
    --to=arigead@gmail.com \
    --cc=linux-can@vger.kernel.org \
    /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).