From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753788AbcDKIm3 (ORCPT ); Mon, 11 Apr 2016 04:42:29 -0400 Received: from szxga01-in.huawei.com ([58.251.152.64]:5776 "EHLO szxga01-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753062AbcDKImZ (ORCPT ); Mon, 11 Apr 2016 04:42:25 -0400 Subject: Re: [PATCH v8 0/5] Add Support for Hi6220 PMIC Hi6553 MFD Core To: Lee Jones References: <1455431363-113771-1-git-send-email-puck.chen@hisilicon.com> <20160411081446.GC4592@x1> CC: , , , , , , , From: Chen Feng Message-ID: <570B6338.3000006@hisilicon.com> Date: Mon, 11 Apr 2016 16:41:28 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: <20160411081446.GC4592@x1> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.142.193.64] X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.570B634F.0055,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: 9ded90b68f037db94c2d87c63043ab18 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi lee, Mark already took the regulator set. Please help take the mfd part. mfd: hi655x: Add document for mfd hi665x PMIC and mfd: hi655x: Add MFD driver for hi655x thanks a lot. On 2016/4/11 16:14, Lee Jones wrote: > On Sun, 14 Feb 2016, Chen Feng wrote: > >> 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. >> >> V8: Change format in document, and fix bit mask in regulator. >> >> 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 > > So what's going on with this set? Can the MFD patches go in via my > tree on their own? Or are there dependencies between them and the > Regulator changes? If the latter, then we need Mark's Ack to > proceed. > >> .../devicetree/bindings/mfd/hisilicon,hi655x.txt | 27 +++ >> .../regulator/hisilicon,hi655x-regulator.txt | 29 +++ >> 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 | 55 +++++ >> 10 files changed, 607 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 >> >