[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150604143457.2a0e0acf@north>
Date: Thu, 4 Jun 2015 14:34:57 +0200
From: Jakub KiciĆski <moorray3@...pl>
To: <linux-serial@...r.kernel.org>, <devicetree@...r.kernel.org>
Cc: Cyrille Pitchen <cyrille.pitchen@...el.com>,
<nicolas.ferre@...el.com>, <gregkh@...uxfoundation.org>,
<wenyou.yang@...el.com>, <ludovic.desroches@...el.com>,
<leilei.zhao@...el.com>, <josh.wu@...el.com>,
<alexandre.belloni@...e-electrons.com>,
<linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>, <galak@...eaurora.org>,
<ijc+devicetree@...lion.org.uk>, <mark.rutland@....com>,
<pawel.moll@....com>, <robh+dt@...nel.org>
Subject: Re: [PATCH linux-next 1/4] ARM: at91/dt: add new DT properties for
Atmel usart
On Tue, 2 Jun 2015 16:18:21 +0200, Cyrille Pitchen wrote:
> +- atmel,rts-low-threshold: when the RX FIFO level, ie the number of data
> + available to be read from the RX FIFO, crosses down this threshold the RTS
> + line is driven to low level to tell the remote peer that it can (re)start
> + sending new data.
> +- atmel,rts-high-threshold: when the RX FIFO level crosses up this threshold,
> + the RTS line is driven to high level to tell the remote peer that it should
> + stop sending new data.
Maintainers, are there any guidelines for what is appropriate to put
into DT? The parameters above look like they could be programmed at
runtime through some user space API like sysfs.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists