From: Mark Brown <broonie@kernel.org>
To: Flora Fu <flora.fu@mediatek.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Matthias Brugger <matthias.bgg@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Rob Herring <robh+dt@kernel.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Lee Jones <lee.jones@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
arm@kernel.org, Mark Rutland <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Russell King <linux@arm.linux.org.uk>,
srv_heupstream <srv_heupstream@mediatek.com>,
Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
HenryC Chen <henryc.chen@mediatek.com>,
Menghui Lin <menghui.lin@mediatek.com>,
Olof Johansson <olof@lixom.net>,
Sascha Hauer <kernel@pengutronix.de>,
Kumar Gala <galak@codeaurora.org>,
Grant Likely <grant.likely@linaro.org>,
Yingjoe Chen <yingjoe.chen@mediatek.com>,
Eddie Huang <eddie.huang@mediatek.com>,
Dongdong Cheng <dongdong.cheng@mediatek.com>
Subject: Re: [PATCH v3 1/8] soc: mediatek: Add PMIC wrapper for MT8135 and MT6397 SoC
Date: Mon, 15 Dec 2014 17:22:02 +0000 [thread overview]
Message-ID: <20141215172202.GI11764@sirena.org.uk> (raw)
In-Reply-To: <1418292255.2315.12.camel@mtksdaap41>
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
On Thu, Dec 11, 2014 at 06:04:15PM +0800, Flora Fu wrote:
> On Tue, 2014-12-09 at 12:20 +0100, Arnd Bergmann wrote:
> > If it looks like i2c messages, would it be more appropriate to make
> > it appear as an i2c controller then?
> Although the message looks like I2C command, it is not I2C.
> Form source code, the software does not touch any I2C i/o or protocols.
> It depends SoC and has specific initial flow, read and write transfer
> state. It is not able to an i2c controller.
What Arnd is suggesting is that if the flow for using it is similar
enough to I2C you can push it through the I2C framework anyway even
though it'll never be possible to use it with generic devices.
> That's why we consider its a proprietary hardware with specific
> protocols. How about let it appear in driver/soc?
That's another option, though I'm not sure that's what the arm-soc
people are looking for.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-12-15 17:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 4:07 [PATCH v3 0/8] Add Support for MediaTek PMIC MT6397 MFD Core and Regulator Flora Fu
2014-12-05 4:07 ` [PATCH v3 1/8] soc: mediatek: Add PMIC wrapper for MT8135 and MT6397 SoC Flora Fu
2014-12-05 10:13 ` Arnd Bergmann
2014-12-09 2:15 ` Flora Fu
2014-12-09 8:23 ` Arnd Bergmann
2014-12-09 10:13 ` Sascha Hauer
2014-12-09 10:30 ` Matthias Brugger
2014-12-09 11:20 ` Arnd Bergmann
2014-12-11 10:04 ` Flora Fu
2014-12-14 20:18 ` Arnd Bergmann
2014-12-15 17:22 ` Mark Brown [this message]
2014-12-05 4:07 ` [PATCH v3 2/8] mfd: MT6397: Add support for PMIC MT6397 MFD Flora Fu
2014-12-08 8:46 ` Lee Jones
2014-12-05 4:07 ` [PATCH v3 3/8] regulator: MT6397: Add support for MT6397 regulator Flora Fu
2014-12-24 12:41 ` Mark Brown
2014-12-05 4:07 ` [PATCH v3 4/8] dt-bindings:: Add document for MT8135 PMIC Wrapper Flora Fu
2014-12-05 4:07 ` [PATCH v3 5/8] dt-bindings: Add document for MT6397 MFD Flora Fu
2014-12-05 4:07 ` [PATCH v3 6/8] dt-bindings: Add document for MT6397 regulator Flora Fu
2014-12-24 12:41 ` Mark Brown
2014-12-05 4:07 ` [PATCH v3 7/8] ARM: dts: mt8135: Add support for MT8135 PMIC wrapper Flora Fu
2014-12-05 4:07 ` [PATCH v3 8/8] ARM: dts: mt8135: Add support for MT6397 MFD and regulator Flora Fu
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=20141215172202.GI11764@sirena.org.uk \
--to=broonie@kernel.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=dongdong.cheng@mediatek.com \
--cc=eddie.huang@mediatek.com \
--cc=flora.fu@mediatek.com \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=henryc.chen@mediatek.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kernel@pengutronix.de \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=menghui.lin@mediatek.com \
--cc=olof@lixom.net \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sameo@linux.intel.com \
--cc=srv_heupstream@mediatek.com \
--cc=yingjoe.chen@mediatek.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
all inboxes | Powered by JetHome®