[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <02E7334B1630744CBDC55DA85862258349301CAD@ORSMSX102.amr.corp.intel.com>
Date: Wed, 20 May 2015 17:22:51 +0000
From: "Yang, Fei" <fei.yang@...el.com>
To: Mark Brown <broonie@...nel.org>,
"Zha, Qipeng" <qipeng.zha@...el.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Zhong, Huiquan" <huiquan.zhong@...el.com>,
"Chen, Jason CJ" <jason.cj.chen@...el.com>,
"Zheng, Qi" <qi.zheng@...el.com>
Subject: RE: [PATCH] regmap: add virtual PMIC IPC bus support
>> 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists