linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: linux-fbdev@vger.kernel.org, linux-omap@vger.kernel.org,
	Archit Taneja <archit@ti.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/4] SiI9022 HDMI encoder for AM4xxx boards
Date: Thu, 03 Jul 2014 16:34:46 +0200	[thread overview]
Message-ID: <87k37u7bp5.fsf@lebrac.rtp-net.org> (raw)
In-Reply-To: <1404394800-18138-1-git-send-email-tomi.valkeinen@ti.com> (Tomi Valkeinen's message of "Thu, 3 Jul 2014 16:39:56 +0300")

Tomi Valkeinen <tomi.valkeinen@ti.com> writes:

> Hi,

Hi,

>
> This series adds a driver for SiI9022 HDMI encoder, which is used on AM437x GP
> and AM43x EPOS boards.
>
> The series is based on the OMAPDSS HDMI infoframe series sent earlier, as the
> SiI9022 driver uses the new infoframe support.

Is there any small possibility to not make it an omap specific driver?
There are other boards with sii9022 out there. imx5x dev boards could
receive a daughter board with this chip (both sold by Freescale) and
efikamx platform has it too. I think that some old msm platforms has it
too.
I've not compared the code of the drivers and don't know how the sii9022
works but would be annoying to have 2 or more drivers for the same piece
of HW. imho, it would be nice if it could be avoided.

Thanks,
Arnaud

  parent reply	other threads:[~2014-07-03 14:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-03 13:39 [PATCH 0/4] SiI9022 HDMI encoder for AM4xxx boards Tomi Valkeinen
2014-07-03 13:39 ` [PATCH 1/4] OMAPDSS: add SiI9022 encoder driver Tomi Valkeinen
2014-07-03 13:39 ` [PATCH 2/4] Doc/DT: Add SiI9022 binding documentation Tomi Valkeinen
2014-07-03 13:39 ` [PATCH 3/4] arm/dts: am43x EPOS HDMI support Tomi Valkeinen
2014-07-03 13:40 ` [PATCH 4/4] arm/dts: am437x GP " Tomi Valkeinen
2014-07-03 14:34 ` Arnaud Patard [this message]
2014-07-04  8:02   ` [PATCH 0/4] SiI9022 HDMI encoder for AM4xxx boards Tomi Valkeinen

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=87k37u7bp5.fsf@lebrac.rtp-net.org \
    --to=arnaud.patard@rtp-net.org \
    --cc=archit@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tomi.valkeinen@ti.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;
as well as URLs for NNTP newsgroup(s).