On Mon, Jun 3, 2013 at 2:31 PM, Michal Simek <michal.simek@xxxxxxxxxx> wrote:
> Describe gpio-xilinx binding.
>
> Signed-off-by: Michal Simek <michal.simek@xxxxxxxxxx>
> ---
> Changes in v2:
> - Extend description
Thanks, patch applied but look into this:
> +Optional properties:
> +- interrupts : Interrupt mapping for GPIO IRQ.
> +- interrupt-parent : Phandle for the interrupt controller that
> + services interrupts for this device.
> +- xlnx,all-inputs : if n-th bit is setup, GPIO-n is input
> +- xlnx,dout-default : if n-th bit is 1, GPIO-n default value is 1
> +- xlnx,gpio-width : gpio width
> +- xlnx,tri-default : if n-th bit is 1, GPIO-n is in tristate mode
> +- xlnx,is-dual : if 1, controller also uses the second channel
If is present, xlnx,is-dual;
> +Example:
> +gpio: gpio@40000000 {
> + #gpio-cells = <2>;
> + compatible = "xlnx,xps-gpio-1.00.a";
> + gpio-controller ;
> + interrupt-parent = <µblaze_0_intc>;
> + interrupts = < 6 2 >;
> + reg = < 0x40000000 0x10000 >;
> + xlnx,all-inputs = <0x0>;
> + xlnx,all-inputs-2 = <0x0>;
> + xlnx,dout-default = <0x0>;
> + xlnx,dout-default-2 = <0x0>;
> + xlnx,gpio-width = <0x2>;
> + xlnx,gpio2-width = <0x2>;
> + xlnx,interrupt-present = <0x1>;
> + xlnx,is-dual = <0x1>;
xlnx,is-dual;
I'm not giving up on this suggestion.
Test it please...
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
