linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: Lukas Wunner <lukas@wunner.de>,
	Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Cc: matthias.bgg@kernel.org, linux-arm-kernel@lists.infradead.org,
	Matthias Brugger <mbrugger@suse.com>,
	Scott Branden <sbranden@broadcom.com>,
	gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	Ray Jui <rjui@broadcom.com>, Stephen Boyd <swboyd@chromium.org>,
	Florian Fainelli <f.fainelli@gmail.com>,
	bcm-kernel-feedback-list@broadcom.com,
	linux-rpi-kernel@lists.infradead.org,
	linux-serial@vger.kernel.org, jslaby@suse.com
Subject: Re: [PATCH] serial: 8250_early: Add earlycon for BCM2835 aux uart
Date: Wed, 12 Feb 2020 16:18:21 +0100	[thread overview]
Message-ID: <89b0eeb4-f08b-791e-b0d6-ac2f5bd6330d@gmail.com> (raw)
In-Reply-To: <20200212132834.c63354wynhmrg6hz@wunner.de>



On 12/02/2020 14:28, Lukas Wunner wrote:
> On Mon, Feb 03, 2020 at 08:10:21PM +0100, Nicolas Saenz Julienne wrote:
>> On Fri, 2020-01-31 at 16:24 +0100, Lukas Wunner wrote:
>>> On Thu, Jan 30, 2020 at 05:11:55PM +0100, Nicolas Saenz Julienne wrote:
>>>> BTW did you had the oportunity to have a go at the patch?
>>>
>>> I've just performed a quick test and it doesn't work for me.
>>> If I add stdout-path = "serial1:115200n8"; to the chosen node,
>>> I only get a regular console with this patch, not an earlycon.
>>
>> That's surprising, you're using u-boot isn't it? and the upstream device tree?
> 
> My apologies for the delay.
> 
> We boot the kernel directly from the Foundation's bootloader without
> U-Boot as intermediary, and we use the downstream DT and kernel
> (with RT & custom patches).
> 
> As far as I could see, the 8250_bcm2835aux UART wasn't even found
> when the kernel searched for available earlycons.  The compatible
> string in the DT does match the one in Matthias' patch.
> 

Can you provide your device tree please. I suspect that we find the culprit there.

Regards,
Matthias

> I notice that Greg has already applied the patch to tty/next.
> I'm currently stretched a little thin but I'll debug this further
> once the dust has settled here.
> 
> Thanks,
> 
> Lukas
> 

      reply	other threads:[~2020-02-12 15:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-26 12:33 [PATCH] serial: 8250_early: Add earlycon for BCM2835 aux uart matthias.bgg
2020-01-26 13:12 ` Lukas Wunner
2020-01-26 20:20   ` Matthias Brugger
2020-01-28 12:42     ` Nicolas Saenz Julienne
2020-01-28 14:19       ` Lukas Wunner
2020-01-30 16:11         ` Nicolas Saenz Julienne
2020-01-31 15:24           ` Lukas Wunner
2020-02-03 19:10             ` Nicolas Saenz Julienne
2020-02-12 13:28               ` Lukas Wunner
2020-02-12 15:18                 ` Matthias Brugger [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=89b0eeb4-f08b-791e-b0d6-ac2f5bd6330d@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=matthias.bgg@kernel.org \
    --cc=mbrugger@suse.com \
    --cc=nsaenzjulienne@suse.de \
    --cc=rjui@broadcom.com \
    --cc=sbranden@broadcom.com \
    --cc=swboyd@chromium.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).