From: Lucas Tanure <tanure@linux.com>
To: Neil Armstrong <neil.armstrong@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Kevin Hilman <khilman@baylibre.com>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org
Subject: Re: [PATCH v2] Revert "tty: serial: meson: Add a earlycon for the T7 SoC"
Date: Sun, 27 Aug 2023 11:04:36 +0100 [thread overview]
Message-ID: <09735262-1bc0-40cf-b139-22cccf70bcab@linux.com> (raw)
In-Reply-To: <7bf9e716-0ff2-56d5-07ab-db027901454e@linaro.org>
On 27-08-2023 10:48, Neil Armstrong wrote:
> Hi Lucas,
>
> Le 27/08/2023 à 10:29, Lucas Tanure a écrit :
>> This reverts commit 6a4197f9763325043abf7690a21124a9facbf52e.
>> New SoC will use ttyS0 instead of ttyAML, so T7 SoC doesn't need a
>> OF_EARLYCON_DECLARE.
>>
>> Signed-off-by: Lucas Tanure <tanure@linux.com>
>> ---
>> Since V1:
>> - add Signed-off-by:
>>
>> drivers/tty/serial/meson_uart.c | 2 --
>> 1 file changed, 2 deletions(-)
>>
>> diff --git a/drivers/tty/serial/meson_uart.c
>> b/drivers/tty/serial/meson_uart.c
>> index c4f61d82fb727..790d910dafa5d 100644
>> --- a/drivers/tty/serial/meson_uart.c
>> +++ b/drivers/tty/serial/meson_uart.c
>> @@ -648,8 +648,6 @@ meson_serial_early_console_setup(struct
>> earlycon_device *device, const char *opt
>> OF_EARLYCON_DECLARE(meson, "amlogic,meson-ao-uart",
>> meson_serial_early_console_setup);
>> -OF_EARLYCON_DECLARE(meson, "amlogic,t7-uart",
>> - meson_serial_early_console_setup);
>> #define MESON_SERIAL_CONSOLE_PTR(_devname)
>> (&meson_serial_console_##_devname)
>> #else
>
> How do you use earlycon with this removed ?
>
> Neil
This is my kernel cmdline:
console=ttyS0,921600 no_console_suspend earlycon=ttyS0,0xfe078000
And I can see my log:
boot 64bit kernel
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd092]
[ 0.000000] Linux version 6.5.0-rc7-next-20230825+ (tanureal@ryzen)
(aarch64-none-linux-gnu-gcc (GNU Toolchain for the A-profile
Architecture 10.3-2021.07 (arm-10.29)) 10.3.1 20210621, GNU ld (GNU
Toolchain fo3
[ 0.000000] KASLR disabled due to lack of seed
[ 0.000000] Machine model: Khadas vim4
[ 0.000000] OF: reserved mem: 0x0000000005000000..0x00000000052fffff
(3072 KiB) nomap non-reusable secmon@5000000
[ 0.000000] OF: reserved mem: 0x0000000005300000..0x00000000072fffff
(32768 KiB) nomap non-reusable secmon@5300000
...
[ 0.079368] io scheduler mq-deadline registered
[ 0.079374] io scheduler kyber registered
[ 0.079549] io scheduler bfq registered
[ 0.083373] fe078000.serial: ttyS0 at MMIO 0xfe078000 (irq = 14,
base_baud = 1500000) is a meson_uart
[ 0.083403] printk: console [ttyS0] enabled
As the log is OK, and T7 for now is binding against S4 code we should
drop this patch and add a S4 one if needed.
But just having this log is not enough for testing earlycon?
I am assuming that by just having the log since 0.0000 is a good sign
that earlycon is working.
Could you give further guidance?
Lucas Tanure
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
WARNING: multiple messages have this Message-ID (diff)
From: Lucas Tanure <tanure@linux.com>
To: Neil Armstrong <neil.armstrong@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Kevin Hilman <khilman@baylibre.com>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org
Subject: Re: [PATCH v2] Revert "tty: serial: meson: Add a earlycon for the T7 SoC"
Date: Sun, 27 Aug 2023 11:04:36 +0100 [thread overview]
Message-ID: <09735262-1bc0-40cf-b139-22cccf70bcab@linux.com> (raw)
In-Reply-To: <7bf9e716-0ff2-56d5-07ab-db027901454e@linaro.org>
On 27-08-2023 10:48, Neil Armstrong wrote:
> Hi Lucas,
>
> Le 27/08/2023 à 10:29, Lucas Tanure a écrit :
>> This reverts commit 6a4197f9763325043abf7690a21124a9facbf52e.
>> New SoC will use ttyS0 instead of ttyAML, so T7 SoC doesn't need a
>> OF_EARLYCON_DECLARE.
>>
>> Signed-off-by: Lucas Tanure <tanure@linux.com>
>> ---
>> Since V1:
>> - add Signed-off-by:
>>
>> drivers/tty/serial/meson_uart.c | 2 --
>> 1 file changed, 2 deletions(-)
>>
>> diff --git a/drivers/tty/serial/meson_uart.c
>> b/drivers/tty/serial/meson_uart.c
>> index c4f61d82fb727..790d910dafa5d 100644
>> --- a/drivers/tty/serial/meson_uart.c
>> +++ b/drivers/tty/serial/meson_uart.c
>> @@ -648,8 +648,6 @@ meson_serial_early_console_setup(struct
>> earlycon_device *device, const char *opt
>> OF_EARLYCON_DECLARE(meson, "amlogic,meson-ao-uart",
>> meson_serial_early_console_setup);
>> -OF_EARLYCON_DECLARE(meson, "amlogic,t7-uart",
>> - meson_serial_early_console_setup);
>> #define MESON_SERIAL_CONSOLE_PTR(_devname)
>> (&meson_serial_console_##_devname)
>> #else
>
> How do you use earlycon with this removed ?
>
> Neil
This is my kernel cmdline:
console=ttyS0,921600 no_console_suspend earlycon=ttyS0,0xfe078000
And I can see my log:
boot 64bit kernel
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd092]
[ 0.000000] Linux version 6.5.0-rc7-next-20230825+ (tanureal@ryzen)
(aarch64-none-linux-gnu-gcc (GNU Toolchain for the A-profile
Architecture 10.3-2021.07 (arm-10.29)) 10.3.1 20210621, GNU ld (GNU
Toolchain fo3
[ 0.000000] KASLR disabled due to lack of seed
[ 0.000000] Machine model: Khadas vim4
[ 0.000000] OF: reserved mem: 0x0000000005000000..0x00000000052fffff
(3072 KiB) nomap non-reusable secmon@5000000
[ 0.000000] OF: reserved mem: 0x0000000005300000..0x00000000072fffff
(32768 KiB) nomap non-reusable secmon@5300000
...
[ 0.079368] io scheduler mq-deadline registered
[ 0.079374] io scheduler kyber registered
[ 0.079549] io scheduler bfq registered
[ 0.083373] fe078000.serial: ttyS0 at MMIO 0xfe078000 (irq = 14,
base_baud = 1500000) is a meson_uart
[ 0.083403] printk: console [ttyS0] enabled
As the log is OK, and T7 for now is binding against S4 code we should
drop this patch and add a S4 one if needed.
But just having this log is not enough for testing earlycon?
I am assuming that by just having the log since 0.0000 is a good sign
that earlycon is working.
Could you give further guidance?
Lucas Tanure
WARNING: multiple messages have this Message-ID (diff)
From: Lucas Tanure <tanure@linux.com>
To: Neil Armstrong <neil.armstrong@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Kevin Hilman <khilman@baylibre.com>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org
Subject: Re: [PATCH v2] Revert "tty: serial: meson: Add a earlycon for the T7 SoC"
Date: Sun, 27 Aug 2023 11:04:36 +0100 [thread overview]
Message-ID: <09735262-1bc0-40cf-b139-22cccf70bcab@linux.com> (raw)
In-Reply-To: <7bf9e716-0ff2-56d5-07ab-db027901454e@linaro.org>
On 27-08-2023 10:48, Neil Armstrong wrote:
> Hi Lucas,
>
> Le 27/08/2023 à 10:29, Lucas Tanure a écrit :
>> This reverts commit 6a4197f9763325043abf7690a21124a9facbf52e.
>> New SoC will use ttyS0 instead of ttyAML, so T7 SoC doesn't need a
>> OF_EARLYCON_DECLARE.
>>
>> Signed-off-by: Lucas Tanure <tanure@linux.com>
>> ---
>> Since V1:
>> - add Signed-off-by:
>>
>> drivers/tty/serial/meson_uart.c | 2 --
>> 1 file changed, 2 deletions(-)
>>
>> diff --git a/drivers/tty/serial/meson_uart.c
>> b/drivers/tty/serial/meson_uart.c
>> index c4f61d82fb727..790d910dafa5d 100644
>> --- a/drivers/tty/serial/meson_uart.c
>> +++ b/drivers/tty/serial/meson_uart.c
>> @@ -648,8 +648,6 @@ meson_serial_early_console_setup(struct
>> earlycon_device *device, const char *opt
>> OF_EARLYCON_DECLARE(meson, "amlogic,meson-ao-uart",
>> meson_serial_early_console_setup);
>> -OF_EARLYCON_DECLARE(meson, "amlogic,t7-uart",
>> - meson_serial_early_console_setup);
>> #define MESON_SERIAL_CONSOLE_PTR(_devname)
>> (&meson_serial_console_##_devname)
>> #else
>
> How do you use earlycon with this removed ?
>
> Neil
This is my kernel cmdline:
console=ttyS0,921600 no_console_suspend earlycon=ttyS0,0xfe078000
And I can see my log:
boot 64bit kernel
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd092]
[ 0.000000] Linux version 6.5.0-rc7-next-20230825+ (tanureal@ryzen)
(aarch64-none-linux-gnu-gcc (GNU Toolchain for the A-profile
Architecture 10.3-2021.07 (arm-10.29)) 10.3.1 20210621, GNU ld (GNU
Toolchain fo3
[ 0.000000] KASLR disabled due to lack of seed
[ 0.000000] Machine model: Khadas vim4
[ 0.000000] OF: reserved mem: 0x0000000005000000..0x00000000052fffff
(3072 KiB) nomap non-reusable secmon@5000000
[ 0.000000] OF: reserved mem: 0x0000000005300000..0x00000000072fffff
(32768 KiB) nomap non-reusable secmon@5300000
...
[ 0.079368] io scheduler mq-deadline registered
[ 0.079374] io scheduler kyber registered
[ 0.079549] io scheduler bfq registered
[ 0.083373] fe078000.serial: ttyS0 at MMIO 0xfe078000 (irq = 14,
base_baud = 1500000) is a meson_uart
[ 0.083403] printk: console [ttyS0] enabled
As the log is OK, and T7 for now is binding against S4 code we should
drop this patch and add a S4 one if needed.
But just having this log is not enough for testing earlycon?
I am assuming that by just having the log since 0.0000 is a good sign
that earlycon is working.
Could you give further guidance?
Lucas Tanure
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-27 10:05 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-27 8:29 [PATCH v2] Revert "tty: serial: meson: Add a earlycon for the T7 SoC" Lucas Tanure
2023-08-27 8:29 ` Lucas Tanure
2023-08-27 8:29 ` Lucas Tanure
2023-08-27 9:48 ` Neil Armstrong
2023-08-27 9:48 ` Neil Armstrong
2023-08-27 9:48 ` Neil Armstrong
2023-08-27 10:04 ` Lucas Tanure [this message]
2023-08-27 10:04 ` Lucas Tanure
2023-08-27 10:04 ` Lucas Tanure
2023-08-27 10:23 ` Neil Armstrong
2023-08-27 10:23 ` Neil Armstrong
2023-08-27 10:23 ` Neil Armstrong
2023-08-27 10:31 ` Lucas Tanure
2023-08-27 10:31 ` Lucas Tanure
2023-08-27 10:31 ` Lucas Tanure
2023-08-28 7:58 ` Neil Armstrong
2023-08-28 7:58 ` Neil Armstrong
2023-08-28 7:58 ` Neil Armstrong
2023-08-28 8:20 ` Dmitry Rokosov
2023-08-28 8:20 ` Dmitry Rokosov
2023-08-28 8:20 ` Dmitry Rokosov
2023-08-28 8:23 ` Neil Armstrong
2023-08-28 8:23 ` Neil Armstrong
2023-08-28 8:23 ` Neil Armstrong
2023-08-28 8:46 ` Dmitry Rokosov
2023-08-28 8:46 ` Dmitry Rokosov
2023-08-28 8:46 ` Dmitry Rokosov
2023-08-28 8:47 ` Lucas Tanure
2023-08-28 8:47 ` Lucas Tanure
2023-08-28 8:47 ` Lucas Tanure
2023-08-28 8:50 ` Neil Armstrong
2023-08-28 8:50 ` Neil Armstrong
2023-08-28 8:50 ` Neil Armstrong
2023-08-28 12:31 ` Neil Armstrong
2023-08-28 12:31 ` Neil Armstrong
2023-08-28 12:31 ` Neil Armstrong
2023-08-28 14:47 ` Greg Kroah-Hartman
2023-08-28 14:47 ` Greg Kroah-Hartman
2023-08-28 14:47 ` Greg Kroah-Hartman
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=09735262-1bc0-40cf-b139-22cccf70bcab@linux.com \
--to=tanure@linux.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=neil.armstrong@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.