linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: DSS display-new custom enable/disable hooks
Date: Wed, 25 Sep 2013 09:12:26 +0300	[thread overview]
Message-ID: <52427ECA.1080500@ti.com> (raw)
In-Reply-To: <CAAfyv349Xjt7Wy-R34OW81SzmUX-1WhfVZdbhWVDoOXpUKa9ug@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]

On 24/09/13 23:04, Belisko Marek wrote:
> Hi,
> 
> we're using connector-analog-tv driver to enable TV out on gta04
> board. There is exception that we need to change some twl registers +
> some gpio when enable/disable TV output. My question is if there is
> some way how to do that or do we need to copy'n'paste code from
> connector-analog-tv driver and extend it for handling we need (let's
> call it hack)?

What are those TWL registers and GPIO used for? If they are board
specific things, then I see two options:

- Presuming you're using board files, you could add
platform_enable/disable callbacks to the connector's platform_data, and
make the connector driver call those callbacks.

- Create a new display encoder driver, which handles the TWL and GPIO,
and position it in the video pipeline between VENC and the connector.

The first option is obviously not upstreamable, as it won't work with
DT. And I'm not enthusiastic about merging board specific display
drivers either, but so far I haven't figured better ways to implement
board specific oddities.

 Tomi



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

  reply	other threads:[~2013-09-25  6:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-24 20:04 DSS display-new custom enable/disable hooks Belisko Marek
2013-09-25  6:12 ` Tomi Valkeinen [this message]
2013-09-25  7:09   ` Belisko Marek
2013-09-25  7:45     ` Dr. H. Nikolaus Schaller
2013-09-25  8:29       ` Tomi Valkeinen
2013-09-25  9:00         ` Dr. H. Nikolaus Schaller
2013-09-25 10:50           ` Tomi Valkeinen
2013-09-25 12:26             ` Dr. H. Nikolaus Schaller
2013-09-25 13:57               ` Tomi Valkeinen
2013-09-25 16:11                 ` Dr. H. Nikolaus Schaller
2013-09-26  8:20                   ` Tomi Valkeinen
2013-09-26 11:01                     ` Dr. H. Nikolaus Schaller
2013-09-26 11:49                       ` Tomi Valkeinen
2013-09-26 12:37                         ` Dr. H. Nikolaus Schaller
2013-09-26 12:54                           ` 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=52427ECA.1080500@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=marek.belisko@gmail.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).