From: david.lanzendoerfer@o2s.ch (David Lanzendörfer)
To: linux-arm-kernel@lists.infradead.org
Subject: Naming convention DSI + device tree
Date: Tue, 14 May 2013 20:17:46 +0200 [thread overview]
Message-ID: <20130514181745.GA2762@mail.o2s.ch> (raw)
Hello
I have the following issue:
In order to make the DSI controller react at all, 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);
mdelay(20);
gpio_set_value(TEGRA_GPIO_PH0, 1);
mdelay(10);
gpio_set_value(TEGRA_GPIO_PH2, 1);
mdelay(15);
gpio_set_value(TEGRA_GPIO_PU2, 0);
gpio_set_value(TEGRA_GPIO_PU2, 1);
mdelay(10);
gpio_set_value(TEGRA_GPIO_PU2, 0);
mdelay(10);
gpio_set_value(TEGRA_GPIO_PU2, 1);
mdelay(15);
Now with a device tree comes the question: Where should I put this?
Also because I don't have the schematics of the TF201 (for obvious reasons)
I won't be able to name the pin assignments of the DSI controller
in a generic driver correctly.
Would be neat if an ASUS engineer with the schematic at hand could
figure out what pins these are and could name the pin assignment.
best regards
David
next reply other threads:[~2013-05-14 18:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 18:17 David Lanzendörfer [this message]
2013-05-15 22:28 ` Naming convention DSI + device tree Stephen Warren
2013-05-16 7:15 ` David Lanzendörfer
2013-05-16 18:17 ` Stephen Warren
2013-05-16 19:50 ` David Lanzendörfer
2013-05-17 5:36 ` Alex Courbot
2013-05-17 19:39 ` Stephen Warren
2013-05-22 6:24 ` Mark Zhang
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=20130514181745.GA2762@mail.o2s.ch \
--to=david.lanzendoerfer@o2s.ch \
--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 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).