On 2016-03-07 08:16, Srinivas Kandagatla wrote:
The issue with setting up a fixed clock rate at probe is that it would
overwrite the console rate set by the bootloader for its console
device.
This would result in serial out corruption or missing log when we
system
is booted with earlycon. This
On 2016-04-06 04:26, Stanimir Varbanov wrote:
Some of the peripherals has bam which is controlled by remote
processor, thus the bam dma driver must avoid register writes
which initialise bam hw block. Those registers are protected
from xPU block and any writes to them will lead to secure
violatio
On 2016-04-06 04:26, Stanimir Varbanov wrote:
Currently we write BAM_IRQ_CLR register with zero even when no
BAM_IRQ occured. This write has some bad side effects when the
BAM instance is for the crypto engine. In case of crypto engine
some of the BAM registers are xPU protected and they cannot b
On 2016-03-22 15:25, Stanimir Varbanov wrote:
On 03/22/2016 11:49 AM, Pramod Gurav wrote:
On some QOCM platforms(eg 8996) BAM control registers are managed
remotely
hence can not be accessed by application processor for writes. So skip
the bam_init
for any such platform if DT property is set.
>
>
> On 08/04/15 14:13, Pramod Gurav wrote:
>> There is no bit setting as UART_IPR_RXSTALE_LAST for UART_DM core so do
>> it only for UART core.
>>
>> Signed-off-by: Pramod Gurav
>> --
>>
>> Changes since last version:
>> - Added new macro fo UART_DM_MR1_AUTO_RFR_LEVEL1 instead of modifying
>> e
>> On Wed, Mar 25, 2015 at 12:23:19PM +0530, rtat...@codeaurora.org wrote:
>>> From: Rupesh Tatiya
>>>
>>> USB 2.01+ full-speed devices can have extended descriptor as well
>>> and can support LPM.
>>>
>>> Change-Id: Ic055d51c02651810d3eb7141bab20a090fe8453b
>>
>> We can't take patches with this i
6 matches
Mail list logo
