On 26/09/17 21:54, Jon Hunter wrote:
>
> On 25/09/17 23:35, Dmitry Osipenko wrote:
>> Currently efuse driver requests DMA channel from an arbitrary DMA device,
>> it is not a problem since there is only one DMA provider for Tegra20 yet,
>> but it will become troublesome once another provider would be added.
>>
>> Signed-off-by: Dmitry Osipenko <digetx@xxxxxxxxx>
>> ---
>> arch/arm/boot/dts/tegra20.dtsi | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/arch/arm/boot/dts/tegra20.dtsi b/arch/arm/boot/dts/tegra20.dtsi
>> index fb485a5e63d7..f1579c9a7ef4 100644
>> --- a/arch/arm/boot/dts/tegra20.dtsi
>> +++ b/arch/arm/boot/dts/tegra20.dtsi
>> @@ -600,6 +600,8 @@
>> clock-names = "fuse";
>> resets = <&tegra_car 39>;
>> reset-names = "fuse";
>> + dmas = <&apbdma 0>;
>> + dma-names = "fuse";
>> };
>>
>> pcie@80003000 {
>>
>
> Acked-by: Jon Hunter <jonathanh@xxxxxxxxxx>
Actually, request-id '0' is a valid request. Does this work ok?
Cheers
Jon
--
nvpublic
--
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
