mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
To: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>,
	Heiko Stuebner <heiko@sntech.de>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>
Cc: kernel@collabora.com, linux-rockchip@lists.infradead.org,
	 linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: defconfig: enable further Rockchip platform drivers
Date: Thu, 26 Jun 2025 11:31:38 -0400	[thread overview]
Message-ID: <e6b3c842625d9740da2481f9b5893015ac699db0.camel@collabora.com> (raw)
In-Reply-To: <20250626-rk3588-defconfig-v1-1-39a19a41c181@collabora.com>

On Thu, 2025-06-26 at 17:16 +0200, Nicolas Frattaroli wrote:
> The RK3588 SoC, and its sibling, the RK3588S, are supported by
> mainline
> Linux. However, some of its SoC drivers are currently not enabled in
> the
> arm64 defconfig.
> 
> Enable rockchip-dfi, rockchip-rga, and the Rockchip specific
> extensions
> to Hantro as modules.

Personally I don't think the first paragraph adds much, so I'd drop it.
 
Also I feel like you're missing the most important information here,
which is what these modules are used for, so I'd focus on that eg
"Enable configs for rockchip-dfi, rga, hantro, etc. This enables
monitoring of DDR load, usage of the hardware codecs, etc"

> 
> These drivers are also used on other Rockchip SoCs that mainline
> supports, notably RK3566/RK3568, as well as RK3399.
> 
> Suggested-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
> Signed-off-by: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
> ---
>  arch/arm64/configs/defconfig | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/arch/arm64/configs/defconfig
> b/arch/arm64/configs/defconfig
> index
> e071f8f45607dbfd8e00b915b27999949ee0fc88..8b5ecb20ed6450faa0da14a6fdb
> 4cb227a1f735f 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -1789,3 +1789,6 @@ CONFIG_CORESIGHT_STM=m
>  CONFIG_CORESIGHT_CPU_DEBUG=m
>  CONFIG_CORESIGHT_CTI=m
>  CONFIG_MEMTEST=y
> +CONFIG_DEVFREQ_EVENT_ROCKCHIP_DFI=m
> +CONFIG_VIDEO_ROCKCHIP_RGA=m
> +CONFIG_VIDEO_HANTRO_ROCKCHIP=m

You should run make savedefconfig and commit the configs from the
generated defconfig so they're in the right place in the defconfig,
rather than just appending them to end like this.

-- 
Thanks,

Nícolas

      reply	other threads:[~2025-06-26 15:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-26 15:16 Nicolas Frattaroli
2025-06-26 15:31 ` Nícolas F. R. A. Prado [this message]

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=e6b3c842625d9740da2481f9b5893015ac699db0.camel@collabora.com \
    --to=nfraprado@collabora.com \
    --cc=catalin.marinas@arm.com \
    --cc=heiko@sntech.de \
    --cc=kernel@collabora.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=nicolas.frattaroli@collabora.com \
    --cc=will@kernel.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 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®