linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Vostrikov <av.linux.dev@gmail.com>
To: linux-serial@vger.kernel.org, linux-embedded@vger.kernel.org
Subject: MFD device driver on top of UART/RS232
Date: Mon, 16 Nov 2015 19:24:58 +0300	[thread overview]
Message-ID: <564A035A.3050108@gmail.com> (raw)

Hi,

I have an embedded system with microcontroller connected via UART/RS232 port. This microcontroller implements several low-level functions that need to be exposed as device drivers in other subsystems (watchdog, LEDs, HWMON, firmware read/write).

I checked many drivers implemented in the kernel, searched through mail list archives and it looks like there are three different ways to solve this task:
A) most of the devices that are connected using UART have user space program that configures and manages it (either directly or with help of dedicated line discipline, SLIP, SL-CAN, etc)
B) serio - mostly used for input devices
C) direct use of UART port taking control from serial_core.

The best match I have found so far is MFD driver for Atmel Microcontroller on iPaq h3xxx (drivers/mfd/ipaq-micro.c) that follows concept "C)"

Is this a good enough example to use for this task? This platform is a legacy one so I am confused a little if new driver will fit nicely into the mainline.

It would be great if someone could point me to another example to follow or advise better way to implement MFD driver without user space involvement.

Best regards,
Andrey





             reply	other threads:[~2015-11-16 16:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-16 16:24 Andrey Vostrikov [this message]
2015-11-17  7:53 ` MFD device driver on top of UART/RS232 Sascha Hauer
2015-11-17 12:45   ` Andrey Vostrikov
2015-11-17 14:16     ` H. Nikolaus Schaller

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=564A035A.3050108@gmail.com \
    --to=av.linux.dev@gmail.com \
    --cc=linux-embedded@vger.kernel.org \
    --cc=linux-serial@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 read-only IMAP folder(s) and NNTP newsgroup(s).