From: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: Hans Verkuil <hverkuil-cisco@xs4all.nl>,
kernel@collabora.com,
Andrew-CT Chen <andrew-ct.chen@mediatek.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Marc Zyngier <maz@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Tiffany Lin <tiffany.lin@mediatek.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] media: mediatek: vcodec: Drop platform_get_resource(IORESOURCE_IRQ)
Date: Mon, 20 Jun 2022 10:52:54 -0400 [thread overview]
Message-ID: <20220620145254.p52iqrfloteof7py@notapiano> (raw)
In-Reply-To: <8956bb3e-60d7-a882-3672-f2a2f0bf858d@collabora.com>
On Mon, Jun 20, 2022 at 09:58:01AM +0200, AngeloGioacchino Del Regno wrote:
> Il 17/06/22 22:39, Nícolas F. R. A. Prado ha scritto:
> > Commit a1a2b7125e10 ("of/platform: Drop static setup of IRQ resource
> > from DT core") removed support for calling platform_get_resource(...,
> > IORESOURCE_IRQ, ...) on DT-based drivers, but the probe() function of
> > mtk-vcodec's encoder was still making use of it. This caused the encoder
> > driver to fail probe.
> >
> > Since the platform_get_resource() call was only being used to check for
> > the presence of the interrupt (its returned resource wasn't even used)
> > and platform_get_irq() was already being used to get the IRQ, simply
> > drop the use of platform_get_resource(IORESOURCE_IRQ) and handle the
> > failure of platform_get_irq(), to get the driver probing again.
> >
> > Fixes: a1a2b7125e10 ("of/platform: Drop static setup of IRQ resource from DT core")
> > Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
> >
> > ---
> > Tested on mt8192-asurada-spherion.
>
> Yep, that's totally necessary... Except the Fixes tag should be wrong here,
> as you're not fixing that commit, but the mtk-vcodec driver in relation to
> what's happening due to said commit.
>
> I get that you're trying to tell everyone "this is an urgent fix", though,
> and I agree that this *has to* get in v5.19 to avoid breaking this driver.
The commit I'm pointing to in the Fixes tag [1] says "Now that all the DT
drivers have switched to platform_get_irq() we can now safely drop the static
setup of IRQ resource from DT core code.", and while there were patches by the
author [2] to do the required changes on some drivers beforehand, some were
missed, including the mtk-vcodec-enc driver which I fix here. I see at least one
other driver that was missed [3], and it also used the same Fixes tag.
I know that my change isn't meant to be part of the commit in the Fixes, but I
still think it makes the most sense to keep this tag, since its meaning is that
that commit broke the support for this driver and this commit fixes it. Wherever
that commit is applied, this one should too to make sure the mtk-vcodec driver
keeps working.
Thanks,
Nícolas
[1] https://lore.kernel.org/all/20220316200633.28974-1-prabhakar.mahadev-lad.rj@bp.renesas.com/
[2] https://lore.kernel.org/all/20211220011524.17206-1-prabhakar.mahadev-lad.rj@bp.renesas.com/
[3] https://lore.kernel.org/all/20220609161457.69614-1-jean-philippe@linaro.org/
>
> Finally, for the code:
>
> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
>
> ...but I think that you have to send a v2 that drops that Fixes tag.
>
> Cheers,
> Angelo
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-06-20 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 20:39 [PATCH] media: mediatek: vcodec: Drop platform_get_resource(IORESOURCE_IRQ) Nícolas F. R. A. Prado
2022-06-20 7:58 ` AngeloGioacchino Del Regno
2022-06-20 14:52 ` 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=20220620145254.p52iqrfloteof7py@notapiano \
--to=nfraprado@collabora.com \
--cc=andrew-ct.chen@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=kernel@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=maz@kernel.org \
--cc=mchehab@kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh@kernel.org \
--cc=tiffany.lin@mediatek.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