linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: dri-devel@lists.freedesktop.org, linux-sh@vger.kernel.org,
	Simon Horman <horms@verge.net.au>
Subject: Re: [PATCH v2 3/3] ARM: shmobile: marzen: Add Display Unit support
Date: Thu, 14 Mar 2013 22:11:05 +0000	[thread overview]
Message-ID: <51424AF9.3080601@cogentembedded.com> (raw)
In-Reply-To: <3727288.GPvHJIxomY@avalon>

On 15.03.2013 0:11, 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(+)

>>> 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

>> [...]

>>> @@ -147,6 +148,38 @@ static struct platform_device hspi_device = {
>>>    	.num_resources	= ARRAY_SIZE(hspi_resources),
>>>    };
>>>
>>> +/* DU */
>>> +static struct resource rcar_du_resources[] = {
>>> +	[0] = {
>>> +		.name	= "Display Unit",
>>> +		.start	= 0xfff80000,
>>> +		.end	= 0xfffb1007,
>>> +		.flags	= IORESOURCE_MEM,
>>> +	},
>>> +	[1] = {
>>> +		.start	= gic_spi(31),
>>> +		.flags	= IORESOURCE_IRQ,
>>> +	},
>>> +};
>>> +
>>> +static struct rcar_du_platform_data rcar_du_pdata = {
>>> +	.encoders = {
>>> +		[0] = {
>>> +			.encoder = RCAR_DU_ENCODER_VGA,
>>> +		},
>>> +	},
>>> +};
>>> +
>>> +static struct platform_device rcar_du_device = {
>>> +	.name		= "rcar-du",
>>> +	.num_resources	= ARRAY_SIZE(rcar_du_resources),
>>> +	.resource	= rcar_du_resources,
>>> +	.dev	= {
>>> +		.platform_data = &rcar_du_pdata,
>>> +		.coherent_dma_mask = ~0,
>>> +	},
>>> +};
>>> +

>> Are we seeing again SoC device declared in the board file? That simply
>> doesn't scale...

> The goal is obviously to move all that to DT, but there's no DT bindings for
> the DU DRM driver yet.

    I don't see how it justifies dubious non-DT design. Let me tell/remind you 
about the LTSI-3.4 tree where all this stuff can be backported and which 
doesn't have DT support, AFAIR.

WBR, Sergei


  reply	other threads:[~2013-03-14 22:11 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 [this message]
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
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=51424AF9.3080601@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=horms@verge.net.au \
    --cc=laurent.pinchart@ideasonboard.com \
    --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).