[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201106181821.46574.arnd@arndb.de>
Date: Sat, 18 Jun 2011 18:21:46 +0200
From: Arnd Bergmann <arnd@...db.de>
To: linux-arm-kernel@...ts.infradead.org
Cc: Shawn Guo <shawn.guo@...aro.org>, patches@...aro.org,
netdev@...r.kernel.org, devicetree-discuss@...ts.ozlabs.org,
Jason Liu <jason.hui@...aro.org>, linux-kernel@...r.kernel.org,
Jeremy Kerr <jeremy.kerr@...onical.com>,
Sascha Hauer <s.hauer@...gutronix.de>
Subject: Re: [PATCH 1/3] serial/imx: add device tree support
On Saturday 18 June 2011 17:19:12 Shawn Guo wrote:
>
> +Required properties:
> +- compatible : should be "fsl,<soc>-uart", "fsl,imx-uart"
> +- reg : address and length of the register set for the device
> +- interrupts : should contain uart interrupt
> +- id : should be the port ID defined by soc
> +
> +Optional properties:
> +- fsl,has-rts-cts : indicate it has rts-cts
> +- fsl,irda-mode : support irda mode
> +
> +Example:
> +
> +uart@...bc000 {
> + compatible = "fsl,imx51-uart", "fsl,imx-uart";
> + reg = <0x73fbc000 0x4000>;
> + interrupts = <31>;
> + id = <1>;
> + fsl,has-rts-cts;
> +};
Should this also support the "clock-frequency" property that 8250-style
serial ports support [1]?
For the flow-control properties, should we name that more generic? The
same property certainly makes sense for other serial-ports if it does
here. OTOH, I'm not sure it's actually reliable, because it also depends
on whether the other side of the connection and the cable support hw flow
control.
Arnd
[1] http://playground.sun.com/1275/bindings/devices/html/serial-1_0d.html#HDR9
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists