From: Tony Lindgren <tony@atomide.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
Russell King <linux@armlinux.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-omap@vger.kernel.org
Subject: Re: Non-existing config symbols DEBUG_OMAP{3,4,5}UART{1,2}
Date: Thu, 21 Oct 2021 15:58:56 +0300 [thread overview]
Message-ID: <YXFkEEwfeF8+osSr@atomide.com> (raw)
In-Reply-To: <CAKXUXMy0FUv25cUGDnhnv=3pTd7NGjepbHao7QoQw8h0hh3CRw@mail.gmail.com>
Hi,
* Lukas Bulwahn <lukas.bulwahn@gmail.com> [211011 05:39]:
> Dear Tony,
>
> With commit d2b310b0234c ("ARM: debug: Use generic 8250 debug_ll for
> omap2 and omap3/4/5 common uarts"), you added address definitions of
> DEBUG_UART_PHYS for OMAP2, OMAP3, OMAP4 and OMAP5 in
> ./arch/arm/Kconfig.debug.
>
> These definitions depend on:
> - DEBUG_OMAP2UART1 || DEBUG_OMAP3UART1 || DEBUG_OMAP4UART1 ||
> DEBUG_OMAP5UART1, and
> - DEBUG_OMAP2UART2 || DEBUG_OMAP3UART2 || DEBUG_OMAP4UART2 ||
> DEBUG_OMAP5UART2.
>
> As of now, only DEBUG_OMAP2UART{1,2} are defined in
> ./arch/arm/Kconfig.debug, but DEBUG_OMAP{3,4,5}UART{1,2} are not
> defined. Hence, ./scripts/checkkconfigsymbols.py warns here on
> non-existing symbols.
>
> I am unsure about the best way to resolve this issue.
>
> - Would you like to simply reuse the config DEBUG_OMAP2UART{1,2} also
> for OMAP3, OMAP4 and OMAP5? Then, we probably just need to delete the
> dead references
> to DEBUG_OMAP{3,4,5}UART{1,2}. If you consider this further change
> helpful, we could even rename the configs to DEBUG_OMAP2PLUSUART{1,2}
> to make the architecture more specific.
>
> - Do you see the need for separate config definitions for UART{1,2} on
> OMAP3, OMAP4 and OMAP5? Then, we would need to add further definitions
> DEBUG_OMAP{3,4,5}UART{1,2}
> in this file and link those to the specific architecture.
>
> Once the direction is clear, I am happy to provide a patch to address
> this issue or you can quickly take care of this yourself.
The missing ones should be the same as the DEBUG_OMAP2 I think. We still
have these defined in arch/arm/mach-omap2/include/mach/serial.h, so that
can be used to confirm it.
Seems like we can just reuse the DEBUG_OMAP2UART variants, not sure if
we need to rename these to DEBUG_OMAP2PLUSUART variants.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
Russell King <linux@armlinux.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-omap@vger.kernel.org
Subject: Re: Non-existing config symbols DEBUG_OMAP{3,4,5}UART{1,2}
Date: Thu, 21 Oct 2021 15:58:56 +0300 [thread overview]
Message-ID: <YXFkEEwfeF8+osSr@atomide.com> (raw)
In-Reply-To: <CAKXUXMy0FUv25cUGDnhnv=3pTd7NGjepbHao7QoQw8h0hh3CRw@mail.gmail.com>
Hi,
* Lukas Bulwahn <lukas.bulwahn@gmail.com> [211011 05:39]:
> Dear Tony,
>
> With commit d2b310b0234c ("ARM: debug: Use generic 8250 debug_ll for
> omap2 and omap3/4/5 common uarts"), you added address definitions of
> DEBUG_UART_PHYS for OMAP2, OMAP3, OMAP4 and OMAP5 in
> ./arch/arm/Kconfig.debug.
>
> These definitions depend on:
> - DEBUG_OMAP2UART1 || DEBUG_OMAP3UART1 || DEBUG_OMAP4UART1 ||
> DEBUG_OMAP5UART1, and
> - DEBUG_OMAP2UART2 || DEBUG_OMAP3UART2 || DEBUG_OMAP4UART2 ||
> DEBUG_OMAP5UART2.
>
> As of now, only DEBUG_OMAP2UART{1,2} are defined in
> ./arch/arm/Kconfig.debug, but DEBUG_OMAP{3,4,5}UART{1,2} are not
> defined. Hence, ./scripts/checkkconfigsymbols.py warns here on
> non-existing symbols.
>
> I am unsure about the best way to resolve this issue.
>
> - Would you like to simply reuse the config DEBUG_OMAP2UART{1,2} also
> for OMAP3, OMAP4 and OMAP5? Then, we probably just need to delete the
> dead references
> to DEBUG_OMAP{3,4,5}UART{1,2}. If you consider this further change
> helpful, we could even rename the configs to DEBUG_OMAP2PLUSUART{1,2}
> to make the architecture more specific.
>
> - Do you see the need for separate config definitions for UART{1,2} on
> OMAP3, OMAP4 and OMAP5? Then, we would need to add further definitions
> DEBUG_OMAP{3,4,5}UART{1,2}
> in this file and link those to the specific architecture.
>
> Once the direction is clear, I am happy to provide a patch to address
> this issue or you can quickly take care of this yourself.
The missing ones should be the same as the DEBUG_OMAP2 I think. We still
have these defined in arch/arm/mach-omap2/include/mach/serial.h, so that
can be used to confirm it.
Seems like we can just reuse the DEBUG_OMAP2UART variants, not sure if
we need to rename these to DEBUG_OMAP2PLUSUART variants.
Regards,
Tony
_______________________________________________
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:[~2021-10-21 12:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 5:28 Non-existing config symbols DEBUG_OMAP{3,4,5}UART{1,2} Lukas Bulwahn
2021-10-11 5:28 ` Lukas Bulwahn
2021-10-21 12:58 ` Tony Lindgren [this message]
2021-10-21 12:58 ` Tony Lindgren
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=YXFkEEwfeF8+osSr@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lukas.bulwahn@gmail.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 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.