linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Zha, Qipeng" <qipeng.zha@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Yang, Fei" <fei.yang@intel.com>,
	"Zhong, Huiquan" <huiquan.zhong@intel.com>,
	"Chen, Jason CJ" <jason.cj.chen@intel.com>,
	"Zheng, Qi" <qi.zheng@intel.com>
Subject: RE: [PATCH] regmap: add virtual PMIC IPC bus support
Date: Tue, 19 May 2015 04:57:00 +0000	[thread overview]
Message-ID: <C6287702A945AC47BE5DB5DFD4B5C6DD018B6A03@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20150518112109.GZ2761@sirena.org.uk>

Hi

>Why is this being added to the regmap core rather than being implemented
>in using the reg_write() and reg_read() callbacks in the core driver for
>the PMIC?

Thanks. I don't receive this message before in eamil.
Current regmap only support register access  using several bus:  i2c, spi, ac97 ...
But register access for intel pmic are done by hardware ipc, so we add such support in regmap core,
To make pmic subdevice drivers can use generic regmap r/w API to access registers.

 
Best wishes
Qipeng

-----Original Message-----
From: Mark Brown [mailto:broonie@kernel.org] 
Sent: Monday, May 18, 2015 7:21 PM
To: Zha, Qipeng
Cc: linux-kernel@vger.kernel.org; Yang, Fei; Zhong, Huiquan; Chen, Jason CJ; Zheng, Qi
Subject: Re: [PATCH] regmap: add virtual PMIC IPC bus support

On Mon, May 18, 2015 at 08:10:04AM +0000, Zha, Qipeng wrote:
> Hi Broonie
> 
> Can you help comment on this patch ?
> We do really want to leverage current regmap framework to acess intel pmic devices.
> So please evaluate this driver, thanks.

Please don't send contentless pings, and please refer to my original response to one of the copies you sent:

https://lkml.org/lkml/2015/4/20/425

  reply	other threads:[~2015-05-19  4:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20 23:38 [PATCH] regmap: add virtual PMIC IPC bus support qipeng.zha
2015-04-20 16:05 ` Mark Brown
2015-05-18  8:10 ` Zha, Qipeng
2015-05-18 11:21   ` Mark Brown
2015-05-19  4:57     ` Zha, Qipeng [this message]
2015-05-19 12:09       ` Mark Brown
2015-05-20  1:02         ` Zha, Qipeng
2015-05-20 11:04           ` Mark Brown
2015-05-20 17:22             ` Yang, Fei
2015-06-10 15:51           ` Yang, Fei

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=C6287702A945AC47BE5DB5DFD4B5C6DD018B6A03@SHSMSX104.ccr.corp.intel.com \
    --to=qipeng.zha@intel.com \
    --cc=broonie@kernel.org \
    --cc=fei.yang@intel.com \
    --cc=huiquan.zhong@intel.com \
    --cc=jason.cj.chen@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qi.zheng@intel.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;
as well as URLs for NNTP newsgroup(s).