linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: jesper.nilsson@axis.com, devicetree-discuss@lists.ozlabs.org,
	linux-kernel@vger.kernel.org, claudio@evidence.eu.com,
	linux-arm-kernel@lists.infradead.org,
	linux-serial@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: [RFC PATCH] tty/serial: RS485 bindings for device tree
Date: Wed, 12 Oct 2011 14:02:38 +0200	[thread overview]
Message-ID: <4E9581DE.20702@atmel.com> (raw)
In-Reply-To: <3289709.mzRgbAUyPT@wuerfel>

On 10/11/2011 08:41 PM, Arnd Bergmann :
> On Tuesday 11 October 2011 19:28:06 Nicolas Ferre wrote:
>>
>>> +Optional properties:
>>> +- linux,rs485-enabled-at-boot-time: empty property telling to enable the rs485
>>> +  feature at boot time. It can be disabled later with proper ioctl.
>>
>> +- linux,rs485-rx-during-tx: empty property that enable the receiving of data
>> +  even whilst sending data.
> 
> This does not sound too linux specific. If it's a hardware property, don't
> use the 'linux,' prefix and just make it 'rs484-full-duplex' or such.

Ok, I understand. Your remark may also apply to linux,rs485-rts-delay.
So we may end-up with:

- linux,rs485-enabled-at-boot-time
- rs485-rx-during-tx
- rs485-rts-delay

Best regards,
-- 
Nicolas Ferre

      reply	other threads:[~2011-10-12 12:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-11 17:13 [RFC PATCH] tty/serial: RS485 bindings for device tree Nicolas Ferre
2011-10-11 17:28 ` Nicolas Ferre
2011-10-11 18:41   ` Arnd Bergmann
2011-10-12 12:02     ` Nicolas Ferre [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=4E9581DE.20702@atmel.com \
    --to=nicolas.ferre@atmel.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arnd@arndb.de \
    --cc=claudio@evidence.eu.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=jesper.nilsson@axis.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@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 NNTP newsgroup(s).