On 2015/11/19 1:27, Philipp Zabel wrote:
> Am Freitag, den 30.10.2015, 11:19 +0800 schrieb Chen Feng:
>> Add DT bindings documentation for hi6220 SoC reset controller.
>>
>> Signed-off-by: Chen Feng <[email protected]>
>> ---
>>  .../bindings/reset/hisilicon,hi6220-reset.txt      | 34 +++++++++++
>>  include/dt-bindings/reset/hisi,hi6220-resets.h     | 67 
>> ++++++++++++++++++++++
>>  2 files changed, 101 insertions(+)
>>  create mode 100644 
>> Documentation/devicetree/bindings/reset/hisilicon,hi6220-reset.txt
>>  create mode 100644 include/dt-bindings/reset/hisi,hi6220-resets.h
>>
>> diff --git 
>> a/Documentation/devicetree/bindings/reset/hisilicon,hi6220-reset.txt 
>> b/Documentation/devicetree/bindings/reset/hisilicon,hi6220-reset.txt
>> new file mode 100644
>> index 0000000..c74898d
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/reset/hisilicon,hi6220-reset.txt
>> @@ -0,0 +1,34 @@
>> +Hisilicon System Reset Controller
>> +======================================
>> +
>> +Please also refer to reset.txt in this directory for common reset
>> +controller binding usage.
>> +
>> +The reset controller registers are part of the system-ctl block on
>> +hi6220 SoC.
>> +
>> +Required properties:
>> +- compatible: may be "hisilicon,hi6220-sysctrl"
>> +- reg: should be register base and length as documented in the
>> +  datasheet
>> +- #reset-cells: 1, see below
>> +
>> +Example:
>> +sys_ctrl: sys_ctrl@f7030000 {
>> +    compatible = "hisilicon,hi6220-sysctrl", "syscon";
>> +    reg = <0x0 0xf7030000 0x0 0x2000>;
>> +    #clock-cells = <1>;
>> +    #reset-cells = <1>;
>> +};
>> +
>> +Specifying reset lines connected to IP modules
>> +==============================================
>> +example:
>> +
>> +        uart1: uart1@..... {
> 
> uart1: serial@...
> 
Thanks,
I will change this soon.
> regards
> Philipp
> 
> 
> 
> .
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to