SUPERH platform development
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/2] Add R-Car Display Unit support for the Marzen board
Date: Wed, 27 Mar 2013 19:18:26 +0000	[thread overview]
Message-ID: <2147090.G3zcvJnIjL@avalon> (raw)
In-Reply-To: <1364407550-30652-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>

Hi Sergei,

On Wednesday 27 March 2013 23:07:31 Sergei Shtylyov wrote:
> Hello.
> 
> On 03/27/2013 09:05 PM, Laurent Pinchart wrote:
> > Per Simon's request, here are r8a7779 and marzen patches that add support
> > for the display unit, based on the pinctrl API.
> > 
> > The patches are not meant to be merged yet, they will be submitted with
> > the next version of the DU driver.
> > 
> > Sergei, is this more in line with how you want SoC devices to be declared
> > ?
> 
> Yes, it seems exactly how it's done by e.g. arch/arm/mach-davinci/, however
> I thought it was kind of tradition here to register the platform devices
> from array. I.e. you could separate setting the platform data ptr and
> registering the device... I don't have a strong opinion on either approach,
> so I will just follow your example when I'll have to submit an Ether SoC
> device.

The issue with keeping the device in the devices array is that it would get 
registered even if the board doesn't provide any platform data, which is 
probably something we want to avoid.

-- 
Regards,

Laurent Pinchart


      parent reply	other threads:[~2013-03-27 19:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27 18:05 [PATCH 0/2] Add R-Car Display Unit support for the Marzen board Laurent Pinchart
2013-03-27 19:06 ` Sergei Shtylyov
2013-03-27 19:18 ` Laurent Pinchart [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=2147090.G3zcvJnIjL@avalon \
    --to=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