From: Matthias Brugger <matthias.bgg@gmail.com>
To: "Roger Lu (陸瑞傑)" <Roger.Lu@mediatek.com>,
"ribalda@chromium.org" <ribalda@chromium.org>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH] soc: mediatek: mtk-svs: Enable the IRQ later
Date: Tue, 20 Dec 2022 15:50:27 +0100 [thread overview]
Message-ID: <e0d3f5c7-6f6b-ee21-170c-51e5240de114@gmail.com> (raw)
In-Reply-To: <52fb6ccf3fe1cb11f3e330ecc4d9c6cf1225c98a.camel@mediatek.com>
On 20/12/2022 12:03, Roger Lu (陸瑞傑) wrote:
> Hi Matthias Sir,
>
> After applying this patch, SVS probes fail as below on my MT8192 platform. If
> thing isn't too late, please do not merge this patch. I'll ask Ricardo how to
> reproduce this issue and give the correct solution. Thanks in advance.
>
Ok, I just dropped the patch from v6.2-tmp/soc branch.
Regards,
Matthias
> #MT8192 platform SVS probe fail log
> [ 10.209430] SVSB_GPU_LOW: init02 completion timeout
> [ 10.214402] mtk-svs 1100b000.svs: svs start fail: -16
> [ 10.219479] mtk-svs: probe of 1100b000.svs failed with error -16
>
> Hi Ricardo,
>
> Could you share us how you reproduce this issue? I have MT8192 Chromebook and
> can give it a try to reproduce the issue you encountered. Thanks a lot.
>
> Sincerely,
> Roger Lu.
>
> On Fri, 2022-12-16 at 13:47 +0100, Matthias Brugger wrote:
>>
>> On 30/11/2022 12:00, AngeloGioacchino Del Regno wrote:
>> > Il 27/11/22 21:22, Ricardo Ribalda ha scritto:
>> > > If the system does not come from reset (like when is booted via
>> > > kexec()), the peripheral might triger an IRQ before the data structures
>> > > are initialised.
>> > >
>> > > Fixes:
>> > >
>> > > [ 0.227710] Unable to handle kernel NULL pointer dereference at
>> > > virtual
>> > > address 0000000000000f08
>> > > [ 0.227913] Call trace:
>> > > [ 0.227918] svs_isr+0x8c/0x538
>> > >
>> > > Signed-off-by: Ricardo Ribalda <ribalda@chromium.org>
>> >
>> > Reviewed-by: AngeloGioacchino Del Regno <
>> > angelogioacchino.delregno@collabora.com>
>> >
>> >
>>
>> Applied thanks!
>>
>
> ************* MEDIATEK Confidentiality Notice ********************
> The information contained in this e-mail message (including any
> attachments) may be confidential, proprietary, privileged, or otherwise
> exempt from disclosure under applicable laws. It is intended to be
> conveyed only to the designated recipient(s). Any use, dissemination,
> distribution, printing, retaining or copying of this e-mail (including its
> attachments) by unintended recipient(s) is strictly prohibited and may
> be unlawful. If you are not an intended recipient of this e-mail, or believe
> that you have received this e-mail in error, please notify the sender
> immediately (by replying to this e-mail), delete any and all copies of
> this e-mail (including any attachments) from your system, and do not
> disclose the content of this e-mail to any other person. Thank you!
WARNING: multiple messages have this Message-ID (diff)
From: Matthias Brugger <matthias.bgg@gmail.com>
To: "Roger Lu (陸瑞傑)" <Roger.Lu@mediatek.com>,
"ribalda@chromium.org" <ribalda@chromium.org>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH] soc: mediatek: mtk-svs: Enable the IRQ later
Date: Tue, 20 Dec 2022 15:50:27 +0100 [thread overview]
Message-ID: <e0d3f5c7-6f6b-ee21-170c-51e5240de114@gmail.com> (raw)
In-Reply-To: <52fb6ccf3fe1cb11f3e330ecc4d9c6cf1225c98a.camel@mediatek.com>
On 20/12/2022 12:03, Roger Lu (陸瑞傑) wrote:
> Hi Matthias Sir,
>
> After applying this patch, SVS probes fail as below on my MT8192 platform. If
> thing isn't too late, please do not merge this patch. I'll ask Ricardo how to
> reproduce this issue and give the correct solution. Thanks in advance.
>
Ok, I just dropped the patch from v6.2-tmp/soc branch.
Regards,
Matthias
> #MT8192 platform SVS probe fail log
> [ 10.209430] SVSB_GPU_LOW: init02 completion timeout
> [ 10.214402] mtk-svs 1100b000.svs: svs start fail: -16
> [ 10.219479] mtk-svs: probe of 1100b000.svs failed with error -16
>
> Hi Ricardo,
>
> Could you share us how you reproduce this issue? I have MT8192 Chromebook and
> can give it a try to reproduce the issue you encountered. Thanks a lot.
>
> Sincerely,
> Roger Lu.
>
> On Fri, 2022-12-16 at 13:47 +0100, Matthias Brugger wrote:
>>
>> On 30/11/2022 12:00, AngeloGioacchino Del Regno wrote:
>> > Il 27/11/22 21:22, Ricardo Ribalda ha scritto:
>> > > If the system does not come from reset (like when is booted via
>> > > kexec()), the peripheral might triger an IRQ before the data structures
>> > > are initialised.
>> > >
>> > > Fixes:
>> > >
>> > > [ 0.227710] Unable to handle kernel NULL pointer dereference at
>> > > virtual
>> > > address 0000000000000f08
>> > > [ 0.227913] Call trace:
>> > > [ 0.227918] svs_isr+0x8c/0x538
>> > >
>> > > Signed-off-by: Ricardo Ribalda <ribalda@chromium.org>
>> >
>> > Reviewed-by: AngeloGioacchino Del Regno <
>> > angelogioacchino.delregno@collabora.com>
>> >
>> >
>>
>> Applied thanks!
>>
>
> ************* MEDIATEK Confidentiality Notice ********************
> The information contained in this e-mail message (including any
> attachments) may be confidential, proprietary, privileged, or otherwise
> exempt from disclosure under applicable laws. It is intended to be
> conveyed only to the designated recipient(s). Any use, dissemination,
> distribution, printing, retaining or copying of this e-mail (including its
> attachments) by unintended recipient(s) is strictly prohibited and may
> be unlawful. If you are not an intended recipient of this e-mail, or believe
> that you have received this e-mail in error, please notify the sender
> immediately (by replying to this e-mail), delete any and all copies of
> this e-mail (including any attachments) from your system, and do not
> disclose the content of this e-mail to any other person. Thank you!
_______________________________________________
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-12-20 14:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-27 20:22 [PATCH] soc: mediatek: mtk-svs: Enable the IRQ later Ricardo Ribalda
2022-11-27 20:22 ` Ricardo Ribalda
2022-11-30 11:00 ` AngeloGioacchino Del Regno
2022-11-30 11:00 ` AngeloGioacchino Del Regno
2022-12-16 12:47 ` Matthias Brugger
2022-12-16 12:47 ` Matthias Brugger
2022-12-20 11:03 ` Roger Lu (陸瑞傑)
2022-12-20 11:03 ` Roger Lu (陸瑞傑)
2022-12-20 12:49 ` AngeloGioacchino Del Regno
2022-12-20 12:49 ` AngeloGioacchino Del Regno
2022-12-20 14:50 ` Matthias Brugger [this message]
2022-12-20 14:50 ` Matthias Brugger
2022-12-20 20:44 ` Ricardo Ribalda
2022-12-20 20:44 ` Ricardo Ribalda
2022-12-20 21:37 ` Ricardo Ribalda
2022-12-20 21:37 ` Ricardo Ribalda
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=e0d3f5c7-6f6b-ee21-170c-51e5240de114@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=Roger.Lu@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=ribalda@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.