2018-01-18 19:02 GMT+08:00 Arnd Bergmann <[email protected]>:
> On Mon, Jan 15, 2018 at 6:53 AM, Greentime Hu <[email protected]> wrote:
>> From: Greentime Hu <[email protected]>
>>
>> This patch adds nds32 CPU binding documents.
>>
>> Signed-off-by: Vincent Chen <[email protected]>
>> Signed-off-by: Rick Chen <[email protected]>
>> Signed-off-by: Zong Li <[email protected]>
>> Signed-off-by: Greentime Hu <[email protected]>
>> Reviewed-by: Rob Herring <[email protected]>
>> ---
>>  Documentation/devicetree/bindings/nds32/cpus.txt |   37 
>> ++++++++++++++++++++++
>>  1 file changed, 37 insertions(+)
>>  create mode 100644 Documentation/devicetree/bindings/nds32/cpus.txt
>>
>> diff --git a/Documentation/devicetree/bindings/nds32/cpus.txt 
>> b/Documentation/devicetree/bindings/nds32/cpus.txt
>> new file mode 100644
>> index 0000000..9a52937
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/nds32/cpus.txt
>> @@ -0,0 +1,37 @@
>> +* Andestech Processor Binding
>> +
>> +This binding specifies what properties must be available in the device tree
>> +representation of a Andestech Processor Core, which is the root node in the
>> +tree.
>> +
>> +Required properties:
>> +
>> +       - compatible:
>> +               Usage: required
>> +               Value type: <string>
>> +               Definition: should be one of:
>> +                       "andestech,n13"
>> +                       "andestech,n15"
>> +                       "andestech,d15"
>> +                       "andestech,n10"
>> +                       "andestech,d10"
>> +                       "andestech,nds32v3"
>
> Based on https://lkml.org/lkml/2017/11/27/1290, this should say that
> the device tree should always list 'andestech,nds32v3' as the most
> generic 'compatible' value and list exactly one of the others in
> addition.
>
>        Arnd

Hi, Arnd:

I will remove the others and just left "andestech,nds32v3" in here.

Reply via email to