SUPERH platform development
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 2/4] sh-pfc: sh73a0: Add VCCQ MC0 regulator
Date: Thu, 25 Apr 2013 12:27:32 +0000	[thread overview]
Message-ID: <1698292.2RjPeMUeES@avalon> (raw)
In-Reply-To: <1366840828-17335-3-git-send-email-laurent.pinchart+renesas@ideasonboard.com>

[-- Attachment #1: Type: text/plain, Size: 817 bytes --]

On Thursday 25 April 2013 13:16:49 Mark Brown wrote:
> On Thu, Apr 25, 2013 at 01:18:39PM +0200, Laurent Pinchart wrote:
> > On Thursday 25 April 2013 12:07:18 Mark Brown wrote:
> > > You could use an MMIO regmap providing the performance isn't critical
> > > enough for that to cause problems.
> > 
> > Can you share a regmap object between two separate drivers for two
> > separate
> > platform devices ?
> 
> Yes, this is commonly done with MFDs for example.

I've had a quick look at the code, the regmap is passed through platform data 
to the subdevices. With such an approach I could even pass the lock down to 
the regulator driver (not that it would be a good idea of course).

I'll push the code as-is for now, but I'll this in mind when migrating the PFC 
driver to regmap.

-- 
Regards,

Laurent Pinchart

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  parent reply	other threads:[~2013-04-25 12:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24 22:00 [PATCH v2 2/4] sh-pfc: sh73a0: Add VCCQ MC0 regulator Laurent Pinchart
2013-04-25 11:07 ` Mark Brown
2013-04-25 11:18 ` Laurent Pinchart
2013-04-25 12:16 ` Mark Brown
2013-04-25 12:27 ` Laurent Pinchart [this message]
2013-04-25 12:37 ` Mark Brown
2013-04-25 13:27 ` Linus Walleij

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=1698292.2RjPeMUeES@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