From: Andre Przywara <andre.przywara@arm.com>
To: u-boot@lists.denx.de
Subject: [PATCH] sunxi: support boot console on uart1 for sun8i
Date: Sun, 14 Feb 2021 00:14:31 +0000 [thread overview]
Message-ID: <20210214001431.2f3969e5@slackpad.fritz.box> (raw)
In-Reply-To: <e4833015-3e56-e38a-8038-28ef82f9f7fb@manjaro.org>
On Sat, 13 Feb 2021 19:45:45 +0100
Tobias Schramm <t.schramm@manjaro.org> wrote:
Hi,
> > Which particular SoC or board is this triggered by?
> >
>
> I'm currently using a board with a Sochip S3 SoC, where the boot console
> is on uart1.
>
> > From the SoCs listed as belonging to the MACH_SUN8I "family", I don't
> > see the R40 and V3s having UART1 muxed on PortG, only A23, A33, H3, H5,
> > and A83T have.
> > So can you restrict the conditions?
>
> I can - at least in the commit description. Unfortunately there is no
> real distinction between V3s and S3 in u-boot. I could of course define
> a new "S3" SoC variant and add it to the ifdef for the uart iomux. Would
> you prefer me to do that?
Ah, looking closer it seems that a V3s don't route out those pins, but
is still using the same die as the S3.
So for the sake of this patch we can assume that the V3s has those
pins as well.
I would say, use: (defined(CONFIG_MACH_SUN8I) && !defined(CONFIG_MACH_SUN8I_R40))
Cheers,
Andre.
>
> [...]
>
> > So I'd recommend to leave this out, I will probably send a patch to
> > remove this altogether.
> Ok. I'll leave that out in v2 then.
>
>
> Thanks,
>
> Tobias
prev parent reply other threads:[~2021-02-14 0:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 14:08 [PATCH] sunxi: support boot console on uart1 for sun8i Tobias Schramm
2021-02-13 17:40 ` Andre Przywara
2021-02-13 18:45 ` Tobias Schramm
2021-02-14 0:14 ` Andre Przywara [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=20210214001431.2f3969e5@slackpad.fritz.box \
--to=andre.przywara@arm.com \
--cc=u-boot@lists.denx.de \
/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