linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Simon Horman <horms@verge.net.au>, dri-devel@lists.freedesktop.org
Cc: linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 3/3] ARM: shmobile: marzen: Add Display Unit support
Date: Wed, 27 Mar 2013 09:49:10 +0000	[thread overview]
Message-ID: <1881729.5FAEJzRRH0@avalon> (raw)
In-Reply-To: <20130327040143.GD25431@verge.net.au>

Hi Simon,

On Wednesday 27 March 2013 13:01:43 Simon Horman wrote:
> On Thu, Mar 14, 2013 at 03:35:46PM +0100, Laurent Pinchart wrote:
> > Only the DU0 VGA output is currently supported. Support for the DU0 LVDS
> > and DU1 LVDS outputs will require information about the panels that will
> > be connected to those outputs.
> > 
> > Signed-off-by: Laurent Pinchart 
> > <laurent.pinchart+renesas@ideasonboard.com>
> > ---
> > 
> >  arch/arm/configs/marzen_defconfig     |  2 ++
> >  arch/arm/mach-shmobile/board-marzen.c | 65 ++++++++++++++++++++++++++++++
> >  2 files changed, 67 insertions(+)

[snip]

> > diff --git a/arch/arm/mach-shmobile/board-marzen.c
> > b/arch/arm/mach-shmobile/board-marzen.c index cdcb799..0020506 100644
> > --- a/arch/arm/mach-shmobile/board-marzen.c
> > +++ b/arch/arm/mach-shmobile/board-marzen.c

[snip]

> > @@ -363,6 +397,37 @@ static void __init marzen_init(void)
> >  	gpio_request(GPIO_FN_HSPI_TX0,	NULL);
> >  	gpio_request(GPIO_FN_HSPI_RX0,	NULL);
> > 
> > +	/* Display Unit 0 (CN10: ARGB0) */
> > +	gpio_request(GPIO_FN_DU0_DR7, NULL);
> > +	gpio_request(GPIO_FN_DU0_DR6, NULL);
> > +	gpio_request(GPIO_FN_DU0_DR5, NULL);
> > +	gpio_request(GPIO_FN_DU0_DR4, NULL);
> > +	gpio_request(GPIO_FN_DU0_DR3, NULL);
> > +	gpio_request(GPIO_FN_DU0_DR2, NULL);
> > +	gpio_request(GPIO_FN_DU0_DR1, NULL);
> > +	gpio_request(GPIO_FN_DU0_DR0, NULL);
> > +	gpio_request(GPIO_FN_DU0_DG7, NULL);
> > +	gpio_request(GPIO_FN_DU0_DG6, NULL);
> > +	gpio_request(GPIO_FN_DU0_DG5, NULL);
> > +	gpio_request(GPIO_FN_DU0_DG4, NULL);
> > +	gpio_request(GPIO_FN_DU0_DG3, NULL);
> > +	gpio_request(GPIO_FN_DU0_DG2, NULL);
> > +	gpio_request(GPIO_FN_DU0_DG1, NULL);
> > +	gpio_request(GPIO_FN_DU0_DG0, NULL);
> > +	gpio_request(GPIO_FN_DU0_DB7, NULL);
> > +	gpio_request(GPIO_FN_DU0_DB6, NULL);
> > +	gpio_request(GPIO_FN_DU0_DB5, NULL);
> > +	gpio_request(GPIO_FN_DU0_DB4, NULL);
> > +	gpio_request(GPIO_FN_DU0_DB3, NULL);
> > +	gpio_request(GPIO_FN_DU0_DB2, NULL);
> > +	gpio_request(GPIO_FN_DU0_DB1, NULL);
> > +	gpio_request(GPIO_FN_DU0_DB0, NULL);
> > +	gpio_request(GPIO_FN_DU0_EXVSYNC_DU0_VSYNC, NULL);
> > +	gpio_request(GPIO_FN_DU0_EXHSYNC_DU0_HSYNC, NULL);
> > +	gpio_request(GPIO_FN_DU0_DOTCLKOUT0, NULL);
> > +	gpio_request(GPIO_FN_DU0_DOTCLKOUT1, NULL);
> > +	gpio_request(GPIO_FN_DU0_DISP, NULL);
> > +
> >  	/* USB (CN21) */
> >  	gpio_request(GPIO_FN_USB_OVC0, NULL);
> >  	gpio_request(GPIO_FN_USB_OVC1, NULL);
> 
> Hi Laurent,
> 
> do you have a version of this patch that will work in conjunction with
> recent pinctrl changes and adds an entry/entries to marzen_pinctrl_map[]
> instead of calling gpio_request?

I'm working on that, the next version will use the pinctrl API. Do you need an 
early patch ?

-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2013-03-27  9:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-14 14:35 [PATCH v2 0/3] R-Car Display Unit DRM driver Laurent Pinchart
2013-03-14 14:35 ` [PATCH v2 1/3] r8a7779: Add Display Unit clock support Laurent Pinchart
2013-03-14 14:35 ` [PATCH v2 2/3] drm: Renesas R-Car Display Unit DRM driver Laurent Pinchart
2013-03-14 14:35 ` [PATCH v2 3/3] ARM: shmobile: marzen: Add Display Unit support Laurent Pinchart
2013-03-14 17:34   ` Sergei Shtylyov
2013-03-14 20:11     ` Laurent Pinchart
2013-03-14 22:11       ` Sergei Shtylyov
2013-03-15  1:36         ` Laurent Pinchart
2013-03-15 12:54           ` Sergei Shtylyov
2013-03-15 12:55   ` Sergei Shtylyov
2013-03-15 13:04     ` Laurent Pinchart
2013-03-27  4:01   ` Simon Horman
2013-03-27  9:49     ` Laurent Pinchart [this message]
2013-03-27 10:44       ` Simon Horman

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=1881729.5FAEJzRRH0@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=horms@verge.net.au \
    --cc=linux-sh@vger.kernel.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).