From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Roger Quadros <rogerq@kernel.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Tony Lindgren <tony@atomide.com>,
"open list:TI ETHERNET SWITCH DRIVER (CPSW)"
<linux-omap@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] memory: OMAP_GPMC should depend on ARCH_OMAP2PLUS || ARCH_K3
Date: Tue, 10 May 2022 10:17:07 +0200 [thread overview]
Message-ID: <CAMuHMdW6VH-N7gx+YtccexE7jprvigJDstu_00FJXtH3d45Wdg@mail.gmail.com> (raw)
In-Reply-To: <5cec89ab-76f7-65d5-0b1d-fdd768234f0e@kernel.org>
Hi Roger,
On Tue, May 10, 2022 at 10:10 AM Roger Quadros <rogerq@kernel.org> wrote:
> On 10/05/2022 11:06, Geert Uytterhoeven wrote:
> > On Tue, May 10, 2022 at 9:40 AM Roger Quadros <rogerq@kernel.org> wrote:
> >> On 10/05/2022 10:30, Geert Uytterhoeven wrote:
> >>> On Tue, May 10, 2022 at 9:22 AM Roger Quadros <rogerq@kernel.org> wrote:
> >>>> On 09/05/2022 16:48, Geert Uytterhoeven wrote:
> >>>>> The Texas Instruments OMAP General Purpose Memory Controller (GPMC) is
> >>>>> only present on TI OMAP2/3/4/5, AM33xx, AM43x, DRA7xx, TI81xx, and K3
> >>>>> SoCs. Hence add a dependency on ARCH_OMAP2PLUS || ARCH_K3, to prevent
> >>>>> asking the user about this driver when configuring a kernel without
> >>>>> OMAP2+ or K3 SoC family support.
> >>>>>
> >>>>> Fixes: be34f45f0d4aa91c ("memory: omap-gpmc: Make OMAP_GPMC config visible and selectable")
> >>>>> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> >
> >> Could you please also add ARCH_KEYSTONE in the 'depends on' list
> >> as some SoCs in that architecture do have the GPMC block.
> >
> > Are you sure? AFAICS, none of the Keystone DTS files have device
> > nodes that are compatible with the match list in the omap-gpmc driver.
>
> Yes, the 66AK2G12 SoC contains the GPMC module. [1]
>
> > Or perhaps the GPMC support still has to be added to the Keystone
> > DTS files (and or driver)?
>
> That's most likely the case.
So would it make sense to compile the omap-gpmc driver on keystone
yet, or does that need the introduction of e.g. a ti,k2g-gpmc compatible
value first, and thus should it be postponed?
> [1] 66AK2G12 datasheet: https://www.ti.com/lit/ds/symlink/66ak2g12.pdf?ts=1652170122865&ref_url=https%253A%252F%252Fwww.ti.com%252Fproduct%252F66AK2G12
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2022-05-10 8:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 13:48 [PATCH] memory: OMAP_GPMC should depend on ARCH_OMAP2PLUS || ARCH_K3 Geert Uytterhoeven
2022-05-10 7:22 ` Roger Quadros
2022-05-10 7:30 ` Geert Uytterhoeven
2022-05-10 7:36 ` Krzysztof Kozlowski
2022-05-10 7:41 ` Roger Quadros
2022-05-10 7:40 ` Roger Quadros
2022-05-10 8:06 ` Geert Uytterhoeven
2022-05-10 8:10 ` Roger Quadros
2022-05-10 8:17 ` Geert Uytterhoeven [this message]
2022-05-10 8:27 ` Roger Quadros
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=CAMuHMdW6VH-N7gx+YtccexE7jprvigJDstu_00FJXtH3d45Wdg@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=rogerq@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).