[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <db42049ab0384d9cb50a9d91ab504796@BY2PR03MB505.namprd03.prod.outlook.com>
Date: Wed, 2 Apr 2014 10:13:07 +0000
From: "Li.Xiubo@...escale.com" <Li.Xiubo@...escale.com>
To: "Li.Xiubo@...escale.com" <Li.Xiubo@...escale.com>,
"broonie@...nel.org" <broonie@...nel.org>
CC: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 2/2] regmap: add DT endianness binding support.
Please discard this patch series:
There has some problems about the commit message, I will resend
this patch series.
> Subject: [PATCH 2/2] regmap: add DT endianness binding support.
>
> For many drivers which will support rich endianness of CPU<-->Dev
> need define DT properties by itself without the binding support.
>
> The value endianness using regmap-mmio, for example:
> Index CPU Device Endianess flag for DT property
> ------------------------------------------------------------
> 1 LE LE -
> 2 LE BE 'little-endian'
Should be 'big-endian' here.
> 3 BE BE -
> 4 BE LE 'big-endian'
>
Should be 'little-endian' here.
> ============
>
> Here add DT endianness binding support will define two string
> properties of the register and value endiannesses:
>
> 'reg-endian' and 'val-endian'.
>
> And the value of them will be:
> 'LE' : REGMAP_ENDIAN_LITTLE
> 'BE' : REGMAP_ENDIAN_BIG
> 'NT' : REGMAP_ENDIAN_NATIVE
> Absent : REGMAP_ENDIAN_DEFAULT
>
> The value endianness using regmap-mmio, for example:
> Index CPU Device Endianess flag for DT property
> ------------------------------------------------------------
> 1 LE LE 'NT' or absent
> 2 LE BE 'LE'
Should be 'BE' here.
> 3 BE BE 'NT' or absent
> 4 BE LE 'BE'
>
Should 'LE' here.
> Please see the following documetation for detail usage:
> Documentation/devicetree/bindings/regmap/regmap-endianness.txt
>
Thanks,
BRs
Xiubo
--
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