From: "Ivan T. Ivanov" <iivanov@suse.de>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: Maxime Ripard <maxime@cerno.tech>,
Guillaume Gardet <Guillaume.Gardet@arm.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
bcm-kernel-feedback-list@broadcom.com, linux-clk@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, nd <nd@arm.com>
Subject: Re: [PATCH v4 0/3] clk: bcm: rpi: Add support for three more clocks
Date: Mon, 11 Jul 2022 10:02:54 +0300 [thread overview]
Message-ID: <b5c560cf5610fa8da1cfd7ef06ca6bac@suse.de> (raw)
In-Reply-To: <ce3e2e21-dc54-1f77-fdbb-6d3627917830@i2se.com>
Hi,
On 2022-07-10 14:12, Stefan Wahren wrote:
> Hi,
>
> Am 10.05.22 um 15:30 schrieb Maxime Ripard:
>> Hi,
>>
>> On Tue, May 10, 2022 at 01:20:18PM +0000, Guillaume Gardet wrote:
>>> May I ask what's the status/plan of this patch series?
>> As far as I know it hasn't been merged yet.
>>
>>> It seems it has not been merged yet, and I know we are a bit late in
>>> the 5.18 schedule, but I think this is a good fix for 5.18.
>> Fix for what? I don't think this series fix any bug?
>
> i think this series (or at least parts of it) is a workaround for this
> issue [1].
No, not really. Bug which this patch set fixes is this one [2].
When using downstream dtb and up to date bootloader index 15 is
valid id RPI_FIRMWARE_VEC_CLK_ID which is used by vc4 module.
>
> We better fix the root cause of the potential out of bounds access in
> clk-raspberrypi properly. I will send a patch soon.
If not mistaken after last rework driver already handle this properly.
clk-raspberrypi.c:362
Regards,
Ivan
>
> [1] - https://github.com/raspberrypi/firmware/issues/1688
[2] https://bugzilla.suse.com/show_bug.cgi?id=1196632
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-07-11 7:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 6:57 [PATCH v4 0/3] clk: bcm: rpi: Add support for three more clocks Ivan T. Ivanov
2022-04-28 6:57 ` [PATCH v4 1/3] clk: bcm: rpi: Add support HEVC clock Ivan T. Ivanov
2022-04-28 6:57 ` [PATCH v4 2/3] clk: bcm: rpi: Handle pixel clock in firmware Ivan T. Ivanov
2022-04-28 6:57 ` [PATCH v4 3/3] clk: bcm: rpi: Add support for VEC clock Ivan T. Ivanov
2022-04-28 8:03 ` Maxime Ripard
2022-05-10 13:20 ` [PATCH v4 0/3] clk: bcm: rpi: Add support for three more clocks Guillaume Gardet
2022-05-10 13:30 ` Maxime Ripard
2022-05-11 6:10 ` Stefan Wahren
2022-05-12 7:57 ` Maxime Ripard
[not found] ` <EA46E084-07A4-4BC9-B9FB-A64102F03867@suse.de>
2022-05-12 8:53 ` Maxime Ripard
2022-07-10 11:12 ` Stefan Wahren
2022-07-11 7:02 ` Ivan T. Ivanov [this message]
2022-07-11 11:55 ` Stefan Wahren
2022-08-23 22:54 ` Stephen Boyd
2022-05-26 11:36 ` Ivan T. Ivanov
2022-06-21 15:30 ` Florian Fainelli
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=b5c560cf5610fa8da1cfd7ef06ca6bac@suse.de \
--to=iivanov@suse.de \
--cc=Guillaume.Gardet@arm.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=maxime@cerno.tech \
--cc=mturquette@baylibre.com \
--cc=nd@arm.com \
--cc=nsaenz@kernel.org \
--cc=sboyd@kernel.org \
--cc=stefan.wahren@i2se.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).