From: Thomas Weber <weber@corscience.de>
To: Koen Kooi <koen.kooi@gmail.com>
Cc: tomi.valkeinen@nokia.com, tony@atomide.com,
linux-omap@vger.kernel.org,
Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH v2] board-omap3-beagle: add DSS2 support
Date: Wed, 14 Apr 2010 12:07:52 +0000 [thread overview]
Message-ID: <4BC5B018.8080102@corscience.de> (raw)
In-Reply-To: <1271242535-23929-1-git-send-email-koen@dominion.thruhere.net>
On 04/14/10 10:55, Koen Kooi wrote:
> This patch adds DSS2 support to the beagleboard boardfile. DVI and TV-out are supported.
>
> Changes since v1:
> * removed beagle_panel_enable_tv() and beagle_panel_disable_tv()
>
> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
> ---
> arch/arm/mach-omap2/board-omap3beagle.c | 130 ++++++++++++++++++++++++-------
> 1 files changed, 103 insertions(+), 27 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/board-omap3beagle.c b/arch/arm/mach-omap2/board-omap3beagle.c
> index 962d377..534316c 100644
> --- a/arch/arm/mach-omap2/board-omap3beagle.c
> +++ b/arch/arm/mach-omap2/board-omap3beagle.c
> @@ -39,6 +39,7 @@
>
<snip>
> +
> +static struct platform_device beagle_dss_device = {
> + .name = "omapdss",
> + .id = -1,
> + .dev = {
> + .platform_data = &beagle_dss_data,
> + },
> +};
> +
> +static struct regulator_consumer_supply beagle_vdac_supply = {
> + .supply = "vdda_dac",
> + .dev = &beagle_dss_device.dev,
> +};
Shouldn't we use the REGULATOR_SUPPLY macro?
see commit ed6543243a1c557dbe2005a86f6d
> +
> +static struct regulator_consumer_supply beagle_vdvi_supply = {
> + .supply = "vdds_dsi",
> + .dev = &beagle_dss_device.dev,
> +};
Here too.
Thomas
prev parent reply other threads:[~2010-04-14 11:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 10:55 [PATCH v2] board-omap3-beagle: add DSS2 support Koen Kooi
2010-04-14 12:07 ` Thomas Weber [this message]
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=4BC5B018.8080102@corscience.de \
--to=weber@corscience.de \
--cc=koen.kooi@gmail.com \
--cc=koen@dominion.thruhere.net \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@nokia.com \
--cc=tony@atomide.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