All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eugeniy.Paltsev@synopsys.com (Eugeniy Paltsev)
To: linux-snps-arc@lists.infradead.org
Subject: DRM: Component framework API support
Date: Thu, 30 Mar 2017 12:05:08 +0000	[thread overview]
Message-ID: <1490875508.6561.11.camel@synopsys.com> (raw)

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.

So what is best way of implementing both component framework API and regular API?in one driver?

Thanks.
-- 
?Eugeniy Paltsev

WARNING: multiple messages have this Message-ID (diff)
From: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
To: "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: DRM: Component framework API support
Date: Thu, 30 Mar 2017 12:05:08 +0000	[thread overview]
Message-ID: <1490875508.6561.11.camel@synopsys.com> (raw)

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.

So what is best way of implementing both component framework API and regular API in one driver?

Thanks.
-- 
 Eugeniy Paltsev

             reply	other threads:[~2017-03-30 12:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-30 12:05 Eugeniy Paltsev [this message]
2017-03-30 12:05 ` DRM: Component framework API support Eugeniy Paltsev
2017-03-30 13:40 ` Jose Abreu
2017-03-30 13:40   ` Jose Abreu

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=1490875508.6561.11.camel@synopsys.com \
    --to=eugeniy.paltsev@synopsys.com \
    --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 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.