Hi Ezequiel,
Thanks for your suggestion.
On Thu, 2021-10-14 at 09:38 -0300, Ezequiel Garcia wrote:
> Hi Yunfei,
>
> On Tue, 12 Oct 2021 at 22:17, yunfei.d...@mediatek.com
> wrote:
> > Hi Ezequiel,
> >
> > Thanks for your feedback,
> >
> > The driver can work well now according to your advice
Hi Yunfei,
On Tue, 12 Oct 2021 at 22:17, yunfei.d...@mediatek.com
wrote:
>
> Hi Ezequiel,
>
> Thanks for your feedback,
>
> The driver can work well now according to your advice with
> of_platform_populate interface.
>
> In order to separate parent node with children node, parent node is
> master
Hi Ezequiel,
Thanks for your feedback,
The driver can work well now according to your advice with
of_platform_populate interface.
In order to separate parent node with children node, parent node is
master device, children node is component device.
The master and component are registered platfor
Hi Yunfei,
> This patch dependents on : "media: mtk-vcodec: support for MT8183 decoder"[1]
> and
> "Mediatek MT8192 clock support"[2].
>
> 1: Multi hardware decode is based on stateless decoder, MT8183 is the first
> time
> to add stateless decoder. Otherwise it will cause conflict. This patch w
Hi Ezequiel,
Thank you for reviewing these series from Yunfei!
This series is one of the main obstacles for us at the moment for MTK
so please continue to help & support reviewing this series.
> > According to google's suggestion, it's better not to use v4l2 async
> > also.
>
> Hum? I haven't see
> > [1]https://patchwork.linuxtv.org/project/linux-media/list/?series=5826
> This link seems to be no longer available.
It is probably because the default state is "Action Required", and
this series was accepted recently afterwards.
I can see the series with the below link.
https://patchwork.linu
On Sun, 26 Sept 2021 at 05:27, yunfei.d...@mediatek.com
wrote:
>
> Hi Ezequiel,
>
> Could you please help to give some feedback when you are free for iommu
> limitation?
>
How about you work on the architecture I originally suggested?
As the saying goes, talk is cheap, show us the code.
So let's
Hi Ezequiel,
Could you please help to give some feedback when you are free for iommu
limitation?
According to google's suggestion, it's better not to use v4l2 async
also.
If there are no further comments, I don't have other choice for this
architecture.
Thanks,
Yunfei Dong
On Tue, 2021-09-14 at
Hi Ezequiel,
On Fri, 2021-09-03 at 11:08 +0800, yunfei.d...@mediatek.com wrote:
> Hi Ezequiel,
>
> Thanks for your suggestion.
> On Thu, 2021-09-02 at 13:30 -0300, Ezequiel Garcia wrote:
> > On Wed, 1 Sept 2021 at 05:32, Yunfei Dong > >
> > wrote:
> > >
> > > This series adds support for multi
On Fri, Sep 3, 2021 at 12:31 AM Ezequiel Garcia
wrote:
>
> On Wed, 1 Sept 2021 at 05:32, Yunfei Dong wrote:
> >
> > This series adds support for multi hardware decode into mtk-vcodec, by first
> > adding component framework to manage each hardware information: interrupt,
> > clock, register bases
Hi Ezequiel,
Thanks for your suggestion.
On Thu, 2021-09-02 at 13:30 -0300, Ezequiel Garcia wrote:
> On Wed, 1 Sept 2021 at 05:32, Yunfei Dong
> wrote:
> >
> > This series adds support for multi hardware decode into mtk-vcodec,
> > by first
> > adding component framework to manage each hardware
On Wed, 1 Sept 2021 at 05:32, Yunfei Dong wrote:
>
> This series adds support for multi hardware decode into mtk-vcodec, by first
> adding component framework to manage each hardware information: interrupt,
> clock, register bases and power. Secondly add core thread to deal with core
> hardware me
12 matches
Mail list logo
