[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <391de5c1-45d7-4773-fe57-7f2bc747214b@microchip.com>
Date: Fri, 25 May 2018 15:17:39 +0300
From: Radu Pirea <radu.pirea@...rochip.com>
To: Richard Genoud <richard.genoud@...il.com>,
<devicetree@...r.kernel.org>, <linux-serial@...r.kernel.org>,
<linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>, <linux-spi@...r.kernel.org>
CC: <mark.rutland@....com>, <robh+dt@...nel.org>,
<lee.jones@...aro.org>, <gregkh@...uxfoundation.org>,
<jslaby@...e.com>, <alexandre.belloni@...tlin.com>,
<nicolas.ferre@...rochip.com>, <broonie@...nel.org>
Subject: Re: [PATCH v3 6/6] tty/serial: atmel: changed the driver to work
under at91-usart mfd
On 05/15/2018 04:14 PM, Richard Genoud wrote:
> On 15/05/2018 14:47, Radu Pirea wrote:
>> On Mon, 2018-05-14 at 12:57 +0200, Richard Genoud wrote:
>>> After your patch, the DMA is not selected anymore:
>>> atmel_usart_serial atmel_usart_serial.0.auto: TX channel not
>>> available, switch to pio
>>> instead of:
>>> atmel_usart fffff200.serial: using dma1chan2 for tx DMA transfers
>>>
>> Fixed.
>>> And the kernel doesn't log anymore on the serial console, despite the
>>> loglevel=8
>>> (after reverting this series, the kernel logs reappears on the serial
>>> console)
>>>
>> Which serial are you using as console?
> fffff200.serial (sam9g35-cm)
> ( stdout-path = "serial0:115200n8"; in the DTS )
>
> With this series applied, all the kernel log goes on the screen.
> Without, it goes on the serial debug.
>
I tested again with archlinux arm and poky-linux4sam release as distros
and kernel log goes on the serial debug. Can you give me more details
like cmdline?
>>> (tests done on sam9g35)
>>>
>> I will consider the rest of suggestions.
>>> regards,
>>> Richard
>
Powered by blists - more mailing lists