From: Ray Jui <ray.jui@broadcom.com>
To: "Clément Péron" <peron.clem@gmail.com>
Cc: "Florian Fainelli" <f.fainelli@gmail.com>,
linux-arm-kernel@lists.infradead.org,
"Russell King" <linux@armlinux.org.uk>,
linux-kernel@vger.kernel.org, "Tony Lindgren" <tony@atomide.com>,
"Laura Abbott" <labbott@redhat.com>,
"Scott Branden" <sbranden@broadcom.com>,
"Jon Mason" <jonmason@broadcom.com>,
"Ray Jui" <rjui@broadcom.com>,
"BCM Kernel Feedback" <bcm-kernel-feedback-list@broadcom.com>,
"Clément Peron" <clement.peron@devialet.com>
Subject: Re: [PATCH v2 1/2] ARM: debug: Add Iproc UART3 debug addresses
Date: Thu, 31 May 2018 10:24:16 -0700 [thread overview]
Message-ID: <41bbf801-f060-2056-4015-b4d05c6831bb@broadcom.com> (raw)
In-Reply-To: <CAJiuCcek9KU6QWsAAxVCLUaf1v97uR6FcLOfY=A1LGCMTmjHjg@mail.gmail.com>
On 5/31/2018 1:22 AM, Clément Péron wrote:
> Hi Rai,
>
> On Wed, 30 May 2018 at 19:25, Ray Jui <ray.jui@broadcom.com> wrote:
>>
>> Hi Clément,
>>
>> Correct me if I'm wrong, but I thought the trend is to move to use
>> earlycon that can be activated from kernel command line for early print
>> before the serial driver is loaded.
>>
>> Have you tried earlcon?
> No, only tested this method.
>
> Thanks,
> Clement
>
If I remember it correctly, I think the trend is to use earlycon. There
are obvious shortcomings by making this configuration compile time based.
>>
>> Thanks,
>>
>> Ray
>>
>> On 5/30/2018 6:19 AM, Clément Péron wrote:
>>> From: Clément Peron <clement.peron@devialet.com>
>>>
>>> Broadcom Iproc SoCs typically use the UART3 for
>>> debug/console, provide a known good location for that.
>>>
>>> Signed-off-by: Clément Peron <clement.peron@devialet.com>
>>> ---
>>>
>>> arch/arm/Kconfig.debug | 12 +++++++++++-
>>> 1 file changed, 11 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/arch/arm/Kconfig.debug b/arch/arm/Kconfig.debug
>>> index 199ebc1c4538..4ea9d5793b91 100644
>>> --- a/arch/arm/Kconfig.debug
>>> +++ b/arch/arm/Kconfig.debug
>>> @@ -207,6 +207,14 @@ choice
>>> depends on ARCH_BCM_HR2
>>> select DEBUG_UART_8250
>>>
>>> + config DEBUG_BCM_IPROC_UART3
>>> + bool "Kernel low-level debugging on BCM IPROC UART3"
>>> + depends on ARCH_BCM_CYGNUS
>>> + select DEBUG_UART_8250
>>> + help
>>> + Say Y here if you want the debug print routines to direct
>>> + their output to the third serial port on these devices.
>>> +
>>> config DEBUG_BCM_KONA_UART
>>> bool "Kernel low-level debugging messages via BCM KONA UART"
>>> depends on ARCH_BCM_MOBILE
>>> @@ -1557,6 +1565,7 @@ config DEBUG_UART_PHYS
>>> default 0x18000400 if DEBUG_BCM_HR2
>>> default 0x18010000 if DEBUG_SIRFATLAS7_UART0
>>> default 0x18020000 if DEBUG_SIRFATLAS7_UART1
>>> + default 0x18023000 if DEBUG_BCM_IPROC_UART3
>>> default 0x1c090000 if DEBUG_VEXPRESS_UART0_RS1
>>> default 0x20001000 if DEBUG_HIP01_UART
>>> default 0x20060000 if DEBUG_RK29_UART0
>>> @@ -1676,6 +1685,7 @@ config DEBUG_UART_VIRT
>>> default 0xf1002000 if DEBUG_MT8127_UART0
>>> default 0xf1006000 if DEBUG_MT6589_UART0
>>> default 0xf1009000 if DEBUG_MT8135_UART3
>>> + default 0xf1023000 if DEBUG_BCM_IPROC_UART3
>>> default 0xf11f1000 if DEBUG_VERSATILE
>>> default 0xf1600000 if DEBUG_INTEGRATOR
>>> default 0xf1c28000 if DEBUG_SUNXI_UART0
>>> @@ -1791,7 +1801,7 @@ config DEBUG_UART_8250_WORD
>>> DEBUG_KEYSTONE_UART0 || DEBUG_KEYSTONE_UART1 || \
>>> DEBUG_ALPINE_UART0 || \
>>> DEBUG_DAVINCI_DMx_UART0 || DEBUG_DAVINCI_DA8XX_UART1 || \
>>> - DEBUG_DAVINCI_DA8XX_UART2 || \
>>> + DEBUG_DAVINCI_DA8XX_UART2 || DEBUG_BCM_IPROC_UART3 || \
>>> DEBUG_BCM_KONA_UART || DEBUG_RK32_UART2
>>>
>>> config DEBUG_UART_8250_PALMCHIP
>>>
next prev parent reply other threads:[~2018-05-31 17:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 13:19 Clément Péron
2018-05-30 13:19 ` [PATCH v2 2/2] ARM: debug: fix BCM2836 order entry Clément Péron
2018-06-04 21:12 ` Florian Fainelli
2018-05-30 17:25 ` [PATCH v2 1/2] ARM: debug: Add Iproc UART3 debug addresses Ray Jui
2018-05-31 8:22 ` Clément Péron
2018-05-31 17:24 ` Ray Jui [this message]
2018-05-31 22:16 ` Florian Fainelli
2018-06-01 17:54 ` Ray Jui
2018-06-04 21:12 ` Florian Fainelli
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=41bbf801-f060-2056-4015-b4d05c6831bb@broadcom.com \
--to=ray.jui@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=clement.peron@devialet.com \
--cc=f.fainelli@gmail.com \
--cc=jonmason@broadcom.com \
--cc=labbott@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=peron.clem@gmail.com \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=tony@atomide.com \
/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
all inboxes | Powered by JetHome®