From: "Yang, Fei" <fei.yang@intel.com>
To: "Zha, Qipeng" <qipeng.zha@intel.com>,
Mark Brown <broonie@kernel.org>,
"Pan, Jacob jun" <jacob.jun.pan@intel.com>,
"Ortiz, Samuel" <samuel.ortiz@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"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: Wed, 10 Jun 2015 15:51:06 +0000 [thread overview]
Message-ID: <02E7334B1630744CBDC55DA85862258349310BBD@ORSMSX102.amr.corp.intel.com> (raw)
In-Reply-To: <C6287702A945AC47BE5DB5DFD4B5C6DD018B845B@SHSMSX104.ccr.corp.intel.com>
> > >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.
> That doesn't really address my concern - we already have the reg_read() and reg_write() interface so devices can use
> regmap without a bus in the core. The question is if this is something that's going to be used by many devices so there's
> code to share or if it's something that's only going to be used by this PMIC in which case keeping it in the driver should be easier.
The IPC code is actually independent of PMIC, it will evolve together with the PMC firmware instead of PMIC. Maintaining the IPC
code inside a PMIC driver would be weird because PMIC doesn't really know/care anything about IPC.
In other words, the same PMIC driver could run on different platforms with either i2c or IPC access without knowing which mechanism is
running underneath.
prev parent reply other threads:[~2015-06-10 15:51 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
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 [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=02E7334B1630744CBDC55DA85862258349310BBD@ORSMSX102.amr.corp.intel.com \
--to=fei.yang@intel.com \
--cc=broonie@kernel.org \
--cc=huiquan.zhong@intel.com \
--cc=jacob.jun.pan@intel.com \
--cc=jason.cj.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qi.zheng@intel.com \
--cc=qipeng.zha@intel.com \
--cc=samuel.ortiz@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).