From: Stefan Wahren <wahrenst@gmx.net>
To: "Ivan T. Ivanov" <iivanov@suse.de>
Cc: sboyd@kernel.org, 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 14:14:25 +0200 [thread overview]
Message-ID: <30874df5-6777-4c7e-91ae-33160abf14a4@gmx.net> (raw)
In-Reply-To: <20240531111857.mwekjpyetqmi7c5t@localhost.localdomain>
Am 31.05.24 um 13:18 schrieb Ivan T. Ivanov:
> On 05-31 13:06, Stefan Wahren wrote:
>> Hi Ivan,
>>
>> Am 31.05.24 um 12:20 schrieb Ivan T. Ivanov:
>>> Hi,
>>>
>>> On 05-31 11:55, Stefan Wahren wrote:
>>>> 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?
>>> I am using few out-of-tree drivers on top of the Andrea's patch-set
>>> and noticed the failure, so decided to prepare the road for RPi5.
>> okay and did you use the vendor DTB or Andreas' version?
> Patches from Andrea don't have "raspberrypi,firmware-clocks" node.
That's the reason i'm asking :-)
>
>>> I am not entirely sure what are you asking.
>> Because Andreas DTS shouldn't require this patch and we usually don't
>> include changes which are not testable with Mainline Kernel.
>>
> So I should wait Andreas' patch set to be merged in before I can post
> anything about RPi5?
No, but it would be extremely helpful for the maintainers to know, which
patches (directly or indirectly) depend on which pending series. So a
comment below the commit message (at the same place as the patch
changelog) about this would be nice in this case.
>
> Regards,
> Ivan
>
prev parent reply other threads:[~2024-05-31 12:14 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
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 [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=30874df5-6777-4c7e-91ae-33160abf14a4@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