Hi,

Rob Herring <r...@kernel.org> writes:
> On Tue, Nov 03, 2015 at 03:36:14PM +0530, Vignesh R wrote:
>> Add qspi memory mapped region entries for AM43xx based SoCs. Also,
>> update the binding documents for the controller to document this change.
>> 
>> Signed-off-by: Vignesh R <vigne...@ti.com>
>
> Acked-by: Rob Herring <r...@kernel.org>
>
>> ---
>>  Documentation/devicetree/bindings/spi/ti_qspi.txt | 5 +++--
>>  arch/arm/boot/dts/am4372.dtsi                     | 4 +++-
>>  2 files changed, 6 insertions(+), 3 deletions(-)
>> 
>> diff --git a/Documentation/devicetree/bindings/spi/ti_qspi.txt 
>> b/Documentation/devicetree/bindings/spi/ti_qspi.txt
>> index f05dd631bef1..05488970060b 100644
>> --- a/Documentation/devicetree/bindings/spi/ti_qspi.txt
>> +++ b/Documentation/devicetree/bindings/spi/ti_qspi.txt
>> @@ -17,9 +17,10 @@ Recommended properties:
>>  
>>  Example:
>>  
>> +For am4372:
>>  qspi: qspi@4b300000 {
>> -    compatible = "ti,dra7xxx-qspi";
>> -    reg = <0x47900000 0x100>, <0x30000000 0x3ffffff>;
>> +    compatible = "ti,am4372-qspi";
>> +    reg = <0x47900000 0x100>, <0x30000000 0x4000000>;
>>      reg-names = "qspi_base", "qspi_mmap";
>>      #address-cells = <1>;
>>      #size-cells = <0>;

and how does the user for this look like ? Don't you need to give this a
proper 'ranges' binding ?

-- 
balbi

Attachment: signature.asc
Description: PGP signature

Reply via email to