From: Chen Feng <puck.chen@hisilicon.com>
To: Lee Jones <lee.jones@linaro.org>, Chen Feng <puck.chen@foxmail.com>
Cc: <linux-kernel@vger.kernel.org>, <lgirdwood@gmail.com>,
<broonie@kernel.org>, <w.f@huawei.com>,
<kong.kongxinwei@hisilicon.com>, <haojian.zhuang@linaro.org>
Subject: Re: [PATCH v7 0/5] Add Support for Hi6220 PMIC Hi6553 MFD Core
Date: Mon, 1 Feb 2016 16:53:11 +0800 [thread overview]
Message-ID: <56AF1CF7.1090903@hisilicon.com> (raw)
In-Reply-To: <20160201083554.GZ3368@x1>
On 2016/2/1 16:35, Lee Jones wrote:
> Somehow you've managed to submit this 0th patch disconnected to the
> remained of the set. This means that when someone either replies to
> the other patches or this one (like now) there will be many mails
> between the two. You may even get complained at for not submitting a
> cover-letter because of it.
>
> Please test your patch-sending system (by sending to only yourself)
> before submitting another set.
>
OK, I will resend this. Sorry about that.
>> The patch sets add support for Hi6220 PMIC Hi655x MFD core and its
>> regulator driver.
>> Current testing and support board is Hikey which is one of 96boards.
>> It is an arm64 open source board. For more information about this board,
>> please access https://www.96boards.org.
>>
>> This is hardware layout for access PMIC Hi655x from AP SoC Hi6220.
>> Between PMIC Hi655x and Hi6220, the physical signal channel is SSI.
>> We can use memory-mapped I/O to communicate.
>>
>> +----------------+ +-------------+
>> | | | |
>> | Hi6220 | SSI bus | Hi655x |
>> | |-------------| |
>> | |(REGMAP_MMIO)| |
>> +----------------+ +-------------+
>>
>> V2: Code refactoring of regulator.
>>
>> V3: Drop mtcmos from this patch and use regmap-irq.
>>
>> V4: Move the vset-table to driver code and donot open code for it.
>>
>> V5: Use regulators_node and of_match, donot open code fot it.
>>
>> V7: Change the constraints into hikey.dts and fix code in PMIC.
>>
>> Chen Feng (5):
>> mfd: hi655x: Add document for mfd hi665x PMIC
>> regulator: hi655x: Document for hi655x regulator
>> mfd: hi655x: Add MFD driver for hi655x
>> regulator: hi655x: enable regulator for hi655x PMIC
>> arm64: dts: hisilicon: Add hi655x pmic dts node
>>
>> .../devicetree/bindings/mfd/hisilicon,hi655x.txt | 27 +++
>> .../regulator/hisilicon,hi655x-regulator.txt | 28 +++
>> arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts | 87 ++++++++
>> drivers/mfd/Kconfig | 10 +
>> drivers/mfd/Makefile | 1 +
>> drivers/mfd/hi655x-pmic.c | 162 +++++++++++++++
>> drivers/regulator/Kconfig | 8 +
>> drivers/regulator/Makefile | 1 +
>> drivers/regulator/hi655x-regulator.c | 227 +++++++++++++++++++++
>> include/linux/mfd/hi655x-pmic.h | 54 +++++
>> 10 files changed, 605 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/mfd/hisilicon,hi655x.txt
>> create mode 100644 Documentation/devicetree/bindings/regulator/hisilicon,hi655x-regulator.txt
>> create mode 100644 drivers/mfd/hi655x-pmic.c
>> create mode 100644 drivers/regulator/hi655x-regulator.c
>> create mode 100644 include/linux/mfd/hi655x-pmic.h
>>
>
prev parent reply other threads:[~2016-02-01 8:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 15:22 Chen Feng
2016-02-01 8:35 ` Lee Jones
2016-02-01 8:53 ` Chen Feng [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=56AF1CF7.1090903@hisilicon.com \
--to=puck.chen@hisilicon.com \
--cc=broonie@kernel.org \
--cc=haojian.zhuang@linaro.org \
--cc=kong.kongxinwei@hisilicon.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=puck.chen@foxmail.com \
--cc=w.f@huawei.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
Powered by JetHome