[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <18e6380f-738f-9c54-ba4b-08e83b134e22@synopsys.com>
Date: Thu, 30 Mar 2017 14:40:14 +0100
From: Jose Abreu <Jose.Abreu@...opsys.com>
To: Eugeniy Paltsev <Eugeniy.Paltsev@...opsys.com>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>
CC: "daniel@...ll.ch" <daniel@...ll.ch>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-snps-arc@...ts.infradead.org"
<linux-snps-arc@...ts.infradead.org>,
"airlied@...ux.ie" <airlied@...ux.ie>
Subject: Re: DRM: Component framework API support
Hi Eugeniy,
On 30-03-2017 13:05, Eugeniy Paltsev wrote:
> Hi,
>
> I am trying to add support of new component framework API in ARC PGU driver.
> The point is that for now we have ARC PGU driver which works with adv7511 encoder. Both of them don't support component framework API. I had to add support of component framework based dw_hdmi encoder to ARC PGU driver.
As of commit 69497eb9 ("drm: bridge: dw-hdmi: Implement DRM
bridge registration") you don't need to use component API, you
can just use a platform driver wrapper.
>
> So what is best way of implementing both component framework API and regular API in one driver?
I guess you want to have support for ADV7511 and dw-hdmi, right?
For component API you need to have a master device which binds
all the components and inits them, for regular API not. I don't
see a clean way to do this (but I'm not that experienced in
component API). Do you need runtime support for both of bridges?
Best regards,
Jose Miguel Abreu
>
> Thanks.
Powered by blists - more mailing lists