Re: [PATCH v4 2/4] drivers: dma: sh: Add DMAC driver for RZ/G2L SoC

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Biju,

On 28-07-21, 07:00, Biju Das wrote:
> > 
> > Sorry I dont like passing numbers like this :(
> > 
> > Can you explain what is meant by each of the above values and looks like
> > some (if not all) can be derived (slave config as well as transaction
> > properties)
> 
> 
> 0x11228 (Tx)
> 0x11220 (Rx)
> 
> BIT 22:- TM :- Transfer Mode 

What are the values, here it seems 0

> Bits 16->19 :- DDS(Destination Data Size) --> 0x0001 (16 bits)
> Bits 12->15 :- SDS(Source Data size)--> 0x0001 (16 bits)

use src_addr_width/dst_addr_width ..?

> Bit  11     :- Reserved
> Bits 8->10 :- Ack mode  --> 0x010 (Bus cycle mode)

What does this mean?

> Bit 7 :-  Reserved
> Bit 6:- LVL -->  Level -->0 (DMA request based on edge of thesignal)
> Bit 5:- HIEN -->  High Enable --> 1 (Detects a DMA request on rising edge of the signal)
> Bit 4:- LOEN --> Low Enable -->0 (Does not DMA request on falling edge of the signal)
> Bit 3:- REQD --> Request Direction ->1 (DMAREQ is Destination)

how and what decides these values

It is now hardcoded in the client driver, can we do that in dma driver
instead? While deriving most of the values?

-- 
~Vinod



[Index of Archives]     [Linux Samsung SOC]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]

  Powered by Linux