All of lore.kernel.org
 help / color / mirror / Atom feed
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: Naming convention DSI + device tree
Date: Wed, 15 May 2013 16:28:50 -0600	[thread overview]
Message-ID: <51940C22.4050802@wwwdotorg.org> (raw)
In-Reply-To: <20130514181745.GA2762@mail.o2s.ch>

On 05/14/2013 12:17 PM, David Lanzend?rfer wrote:
> Hello
> I have the following issue:
> In order to make the DSI controller react at all,

Hmm. In the upstream kernel, we don't even have a DSI driver at all for
Tegra, so control over the panel itself is likely the least of your
worries for now.

> I need to pass him a certain combination of pin states.
> Until now within the code of the original android kernel which was using board files this has just been
> done by doing bit banging.
> 
> namely:
> 	gpio_set_value(tf201_lvds_shutdown, 1);
...
> Now with a device tree comes the question: Where should I put this?

Likely, you will need to create a DT binding that represents the
particular panel model that you have, and make the Tegra display
controller node refer to that panel node. The panel node would need
properties to describe the various GPIOs used to control the panel.
Then, you'd want to write a panel-specific driver that handles that
device tree node.

All of this will likely need to be integrated with the upcoming Common
Display Framework.

  reply	other threads:[~2013-05-15 22:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-14 18:17 Naming convention DSI + device tree David Lanzendörfer
2013-05-15 22:28 ` Stephen Warren [this message]
2013-05-16  7:15   ` David Lanzendörfer
     [not found]     ` <20130516071537.GA13573-cEukqlNQfh4fv37vnLkPlQ@public.gmane.org>
2013-05-16 18:17       ` Stephen Warren
2013-05-16 18:17         ` Stephen Warren
2013-05-16 19:50         ` David Lanzendörfer
2013-05-16 19:50           ` David Lanzendörfer
     [not found]         ` <519522C1.5010107-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-05-17  5:36           ` Alex Courbot
2013-05-17  5:36             ` Alex Courbot
     [not found]             ` <5195C1E2.4020009-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-05-17 19:39               ` Stephen Warren
2013-05-17 19:39                 ` Stephen Warren
2013-05-22  6:24               ` Mark Zhang
2013-05-22  6:24                 ` Mark Zhang
2013-05-23  9:55                 ` Alex Courbot
2013-05-23  9:55                   ` Alex Courbot

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=51940C22.4050802@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=linux-arm-kernel@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.