From: Paul Cercueil <paul@crapouillou.net>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mips <linux-mips@vger.kernel.org>,
MIPS Creator CI20 Development
<mips-creator-ci20-dev@googlegroups.com>
Subject: Re: Usefulness of CONFIG_MACH_JZ47*
Date: Tue, 20 Sep 2022 14:33:13 +0100 [thread overview]
Message-ID: <DBGIIR.8W0JWG83D6FE2@crapouillou.net> (raw)
In-Reply-To: <F21B5D44-94D8-4BDB-BB34-9CBFC5F2B891@goldelico.com>
Le mar., sept. 20 2022 at 14:31:38 +0200, H. Nikolaus Schaller
<hns@goldelico.com> a écrit :
> Hi Paul,
>
>> Am 20.09.2022 um 11:09 schrieb Paul Cercueil <paul@crapouillou.net>:
>>
>> Hi Nikolaus,
>>
>> Le mar., sept. 20 2022 at 08:31:30 +0200, H. Nikolaus Schaller
>> <hns@goldelico.com> a écrit :
>>> Hi Paul,
>>> it seems as if there aren't many places left over where the
>>> MACH_JZ47* configs are still in use:
>>> drivers/char/hw_ramdom/Kconfig
>>> drivers/clk/ingenic/Kconfig
>>> drivers/gpu/drm/ingenic/Kconfig
>>> drivers/pinctrl/pinctrl-ingenic.c
>>> Is it possible to get rid of them and just have
>>> CONFIG_MACH_INGENIC_GENERIC?
>>> This might simplify my defconfig for multiple machines.
>>
>> CONFIG_MIPS_GENERIC_KERNEL=y
>
> This breaks compilation for me, e.g.
>
> arch/mips/mm/cache.c:203:6: error: 'cpu_has_tx39_cache' undeclared
> (first use in this function)
v6.0-rc does not have 'cpu_has_tx39_cache' anywhere in that file, or in
arch/mips/ for that matter. It was removed in v5.18.
And a v5.17 kernel compiles fine here with these options enabled. So
it's a problem on your side, I guess.
>> CONFIG_BOARD_INGENIC=y
>
> This config option does not exist (at least in v6.0-rc). Probably you
> refer to CONFIG_INGENIC_GENERIC_BOARD.
No, I do not, and yes, it exists.
> As far as I see, this does not choose to build any device tree blob.
>
> I tried some patch to get the .dtb built, but the resulting kernel
> does not show any activity.
>
> If I e.g. switch back from CONFIG_INGENIC_GENERIC_BOARD=y to
> CONFIG_JZ4780_CI20=y the kernel works.
Because in the first case you build a generic kernel, which does not
embed any .dtb, and you are responsible for providing the kernel with
the blob at boot time; while if you build with CONFIG_JZ4780_CI20=y it
embeds the .dtb inside the kernel.
You can embed the .dtb into the generic kernel at compile-time too,
have a look at "Kernel type -> Kernel appended dtb support." Not sure
why you'd want that for a generic kernel, though.
>>
>> Then you can support all Ingenic-based boards alongside other MIPS
>> boards.
>
> Yes, I know, but why are the MACH_JZ47* not replaced by
> CONFIG_MACH_INGENIC_GENERIC if they are almost unused or completely
> removed?
They *are* used.
> BTW: there are also seems to be some board specific CONFIGs in
> processor specific code (e.g. CONFIG_JZ4780_CI20 in irqchip code).
rgrep CI20 drivers/irqchip/
returns nothing for me.
> So selecting a MACH is not sufficient to get these features.
>
> All this looks a little fragile and incomplete... Maybe if I find
> some time (which is unfortunately quite unlikely) I can propose some
> fixes.
It is not "fragile and incomplete", it works as intended, and it's a
feature I use often.
-Paul
next prev parent reply other threads:[~2022-09-20 13:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 8:42 [PATCH] rtc: jz4740: Use devm_clk_get_enabled() helper Christophe JAILLET
2022-08-25 22:41 ` Paul Cercueil
2022-09-20 6:31 ` Usefulness of CONFIG_MACH_JZ47* H. Nikolaus Schaller
2022-09-20 9:09 ` Paul Cercueil
2022-09-20 12:31 ` H. Nikolaus Schaller
2022-09-20 13:33 ` Paul Cercueil [this message]
2022-09-20 14:19 ` H. Nikolaus Schaller
2022-09-20 14:46 ` Paul Cercueil
2022-10-13 21:31 ` [PATCH] rtc: jz4740: Use devm_clk_get_enabled() helper Alexandre Belloni
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=DBGIIR.8W0JWG83D6FE2@crapouillou.net \
--to=paul@crapouillou.net \
--cc=hns@goldelico.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=mips-creator-ci20-dev@googlegroups.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).