Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753230AbbFDMfE (ORCPT ); Thu, 4 Jun 2015 08:35:04 -0400 Received: from mx3.wp.pl ([212.77.101.10]:32393 "EHLO mx3.wp.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752332AbbFDMfB (ORCPT ); Thu, 4 Jun 2015 08:35:01 -0400 Date: Thu, 4 Jun 2015 14:34:57 +0200 From: Jakub =?UTF-8?B?S2ljacWEc2tp?= To: , Cc: Cyrille Pitchen , , , , , , , , , , , , , , Subject: Re: [PATCH linux-next 1/4] ARM: at91/dt: add new DT properties for Atmel usart Message-ID: <20150604143457.2a0e0acf@north> In-Reply-To: <6fe7914a2c39245ac9a05cdb9962b88c409ec1a4.1433253787.git.cyrille.pitchen@atmel.com> References: <6fe7914a2c39245ac9a05cdb9962b88c409ec1a4.1433253787.git.cyrille.pitchen@atmel.com> X-Mailer: Claws Mail 3.11.1-85-ga87522 (GTK+ 2.24.28; x86_64-unknown-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-WP-AV: skaner antywirusowy poczty Wirtualnej Polski S. A. X-WP-SPAM: NO 0000000 [gWOk] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 938 Lines: 17 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/