From: "Yang, Fei" <fei.yang@intel.com>
To: Mark Brown <broonie@kernel.org>, "Zha, Qipeng" <qipeng.zha@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, 20 May 2015 17:22:51 +0000 [thread overview]
Message-ID: <02E7334B1630744CBDC55DA85862258349301CAD@ORSMSX102.amr.corp.intel.com> (raw)
In-Reply-To: <20150520110413.GE21577@sirena.org.uk>
>> The detail is
>> Beside pmic core driver itself, there are many pmic function device
>> dirvers, such as gpio, theremal, charger, bcu ..., will use this regmap api to access registers.
> This sounds like this is a single device, not a generic bus.
Well, yes this is more like a bridge to the PMIC instead of a generic bus. In the latest Intel SoC design,
the IA core doesn't have direct access to the I2C bus which PMIC is connected to. Instead, there is a PMC
controlling the I2C host and talking to PMIC directly. In the meantime PMC runs a firmware providing IPC
interface to the IA core. So for IA to access PMIC registers, it has to go through these IPC commands.
In order to fit the regmap architecture, the IPC is treated as a bus here so that the PMIC drivers can be
Implemented in the same way as others.
next prev parent reply other threads:[~2015-05-20 17:22 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 [this message]
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=02E7334B1630744CBDC55DA85862258349301CAD@ORSMSX102.amr.corp.intel.com \
--to=fei.yang@intel.com \
--cc=broonie@kernel.org \
--cc=huiquan.zhong@intel.com \
--cc=jason.cj.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qi.zheng@intel.com \
--cc=qipeng.zha@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).