From: "H. Nikolaus Schaller" <hns@goldelico.com>
To: Andrey Vostrikov <av.linux.dev@gmail.com>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
linux-serial@vger.kernel.org, linux-embedded@vger.kernel.org,
NeilBrown <neil@brown.name>, Marek Belisko <marek@goldelico.com>
Subject: Re: MFD device driver on top of UART/RS232
Date: Tue, 17 Nov 2015 15:16:50 +0100 [thread overview]
Message-ID: <9142F329-3D2D-4B4F-9C18-91CC5B6E3923@goldelico.com> (raw)
In-Reply-To: <564B2166.2030209@gmail.com>
Hi Andrey,
Am 17.11.2015 um 13:45 schrieb Andrey Vostrikov <av.linux.dev@gmail.com>:
> Hi Sascha,
>
> Sascha Hauer wrote:
>> Hi Andrey,
>>
>> +Cc NeilBrown <neil@brown.name>
>>
>> On Mon, Nov 16, 2015 at 07:24:58PM +0300, Andrey Vostrikov wrote:
>>> 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)"
>>
>> There's also D) TTY slave device support: https://lkml.org/lkml/2015/3/18/40
>>
>> Unfortunately this hasn't made it to mainline yet and it seems the
>> parties lost interest after some lengthy discussion of device tree phandles
>> vs. subnodes, but I think this is what you're looking for.
>
> Thank you for pointing out to another option. Looks like it was developed a little further and was submitted as patch by "H. Nikolaus Schaller",
> https://lkml.org/lkml/2015/10/16/729
>
> But I see no further traces of it.
Well, I was still missing a technical discussion of our proposals and a real
evaluation of the benefits of subnode vs. phandle. In my view it was very
ideologic and it was not an exchange of arguments.
> Cc'ed Nikolaus, may be he could comment on state of UART slave patch.
And we are currently working on a compromise. So that the DT developer can
simply choose if he prefers subnode or phandle. And the driver is capable of
handling both. This is not yet finished, so we have not yet submitted an update.
BR,
Nikolaus
prev parent reply other threads:[~2015-11-17 14:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 16:24 MFD device driver on top of UART/RS232 Andrey Vostrikov
2015-11-17 7:53 ` Sascha Hauer
2015-11-17 12:45 ` Andrey Vostrikov
2015-11-17 14:16 ` H. Nikolaus Schaller [this message]
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=9142F329-3D2D-4B4F-9C18-91CC5B6E3923@goldelico.com \
--to=hns@goldelico.com \
--cc=av.linux.dev@gmail.com \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=marek@goldelico.com \
--cc=neil@brown.name \
--cc=s.hauer@pengutronix.de \
/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).