Linux clock framework development
 help / color / mirror / Atom feed
From: Stefan Wahren <wahrenst@gmx.net>
To: "Ivan T. Ivanov" <iivanov@suse.de>, sboyd@kernel.org
Cc: florian.fainelli@broadcom.com, linux-clk@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Maxime Ripard <maxime@cerno.tech>,
	Andrea della Porta <andrea.porta@suse.com>
Subject: Re: [PATCH] clk: bcm: rpi: Add disp clock
Date: Fri, 31 May 2024 11:55:03 +0200	[thread overview]
Message-ID: <4c56e57c-7a4e-4976-a05e-0adf3df13b3f@gmx.net> (raw)
In-Reply-To: <20240531092730.253484-1-iivanov@suse.de>

Hi Ivan,

Am 31.05.24 um 11:27 schrieb Ivan T. Ivanov:
> From: Maxime Ripard <maxime@cerno.tech>
>
> BCM2712 has an extra clock exposed by the firmware called DISP, and used
> by (at least) the HVS. Let's add it to the list of clocks to register in
> Linux.
>
> Without this new definition driver fails at probe on BCM2712.
could you please explain the relation to Andrea's series [1]?

How can this occur, because there is no Raspberry Pi 5 support in Mainline?

[1] -
https://lore.kernel.org/linux-arm-kernel/cover.1717061147.git.andrea.porta@suse.com/
>
> Signed-off-by: Maxime Ripard <maxime@cerno.tech>
> Signed-off-by: Ivan T. Ivanov <iivanov@suse.de>
> ---
>   drivers/clk/bcm/clk-raspberrypi.c          | 5 +++++
>   include/soc/bcm2835/raspberrypi-firmware.h | 1 +
>   2 files changed, 6 insertions(+)
>
> diff --git a/drivers/clk/bcm/clk-raspberrypi.c b/drivers/clk/bcm/clk-raspberrypi.c
> index 4d411408e4af..fabd5595e9cd 100644
> --- a/drivers/clk/bcm/clk-raspberrypi.c
> +++ b/drivers/clk/bcm/clk-raspberrypi.c
> @@ -34,6 +34,7 @@ static char *rpi_firmware_clk_names[] = {
>   	[RPI_FIRMWARE_M2MC_CLK_ID]	= "m2mc",
>   	[RPI_FIRMWARE_PIXEL_BVB_CLK_ID]	= "pixel-bvb",
>   	[RPI_FIRMWARE_VEC_CLK_ID]	= "vec",
> +	[RPI_FIRMWARE_DISP_CLK_ID]	= "disp",
>   };
>
>   #define RPI_FIRMWARE_STATE_ENABLE_BIT	BIT(0)
> @@ -124,6 +125,10 @@ raspberrypi_clk_variants[RPI_FIRMWARE_NUM_CLK_ID] = {
>   	[RPI_FIRMWARE_VEC_CLK_ID] = {
>   		.export = true,
>   	},
> +	[RPI_FIRMWARE_DISP_CLK_ID] = {
> +		.export = true,
> +		.minimize = true,
> +	},
>   };
>
>   /*
> diff --git a/include/soc/bcm2835/raspberrypi-firmware.h b/include/soc/bcm2835/raspberrypi-firmware.h
> index 73cac8d0287e..e1f87fbfe554 100644
> --- a/include/soc/bcm2835/raspberrypi-firmware.h
> +++ b/include/soc/bcm2835/raspberrypi-firmware.h
> @@ -152,6 +152,7 @@ enum rpi_firmware_clk_id {
>   	RPI_FIRMWARE_M2MC_CLK_ID,
>   	RPI_FIRMWARE_PIXEL_BVB_CLK_ID,
>   	RPI_FIRMWARE_VEC_CLK_ID,
> +	RPI_FIRMWARE_DISP_CLK_ID,
>   	RPI_FIRMWARE_NUM_CLK_ID,
>   };
>


  reply	other threads:[~2024-05-31  9:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-31  9:27 [PATCH] clk: bcm: rpi: Add disp clock Ivan T. Ivanov
2024-05-31  9:55 ` Stefan Wahren [this message]
2024-05-31 10:20   ` Ivan T. Ivanov
2024-05-31 11:06     ` Stefan Wahren
2024-05-31 11:18       ` Ivan T. Ivanov
2024-05-31 12:14         ` Stefan Wahren

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=4c56e57c-7a4e-4976-a05e-0adf3df13b3f@gmx.net \
    --to=wahrenst@gmx.net \
    --cc=andrea.porta@suse.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=iivanov@suse.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=maxime@cerno.tech \
    --cc=sboyd@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