From: Jose Abreu <Jose.Abreu@synopsys.com>
To: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Cc: "daniel@ffwll.ch" <daniel@ffwll.ch>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"airlied@linux.ie" <airlied@linux.ie>
Subject: Re: DRM: Component framework API support
Date: Thu, 30 Mar 2017 14:40:14 +0100 [thread overview]
Message-ID: <18e6380f-738f-9c54-ba4b-08e83b134e22@synopsys.com> (raw)
In-Reply-To: <1490875508.6561.11.camel@synopsys.com>
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.
prev parent reply other threads:[~2017-03-30 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 12:05 Eugeniy Paltsev
2017-03-30 13:40 ` Jose Abreu [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=18e6380f-738f-9c54-ba4b-08e83b134e22@synopsys.com \
--to=jose.abreu@synopsys.com \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®