linux-kernel - Re: [PATCH v6 0/4] add syscon driver based on regmap for general registers access

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 5 Sep 2012 13:54:12 +0800
From:	Shawn Guo <shawn.guo@...aro.org>
To:	Dong Aisheng <b29396@...escale.com>,
	Samuel Ortiz <sameo@...ux.intel.com>
Cc:	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	linus.walleij@...ricsson.com, s.hauer@...gutronix.de,
	kernel@...gutronix.de, grant.likely@...retlab.ca,
	rob.herring@...xeda.com, lrg@...com,
	broonie@...nsource.wolfsonmicro.com, richard.zhao@...escale.com,
	devicetree-discuss@...ts.ozlabs.org, swarren@...dotorg.org
Subject: Re: [PATCH v6 0/4] add syscon driver based on regmap for general
 registers access

Hi Samuel,

The series needs to go via mfd or arm-soc tree as a whole.  In case
you want to take it through mfd tree, here is my ack.

Acked-by: Shawn Guo <shawn.guo@...aro.org>

Otherwise, I can take it via arm-soc tree with your ack.

Regards,
Shawn

On Wed, Sep 05, 2012 at 10:57:12AM +0800, Dong Aisheng wrote:
> This patch series mainly adds an syscon driver which is used to access
> general system controller registers like FSL IOMUXC GPR and ANATOP,
> after that, we convert all the exist private access general registers code to use
> standard API from regmap to access registers.
> Finally we remove the old mfd anatop driver which is only for anatop register
> access.
> 
> The patch series is based on linus's tree 3.6-rc4 since commit 5b716ac.
> 
> ChangeLog v5->v6:
>  * put node after call syscon_node_to_regmap in anatop regulator driver
>  * using dev instead of &pdev->dev in syscon probe
> ChangeLog v4->v5:
>  * change syscon driver depends on OF
>  * do not call of_node_put in syscon_node_to_regmap
>  * renamed: include/linux/fsl/imx6q-iomuxc-gpr.h ->
> 	    include/linux/mfd/syscon/imx6q-iomuxc-gpr.h
> ChangeLog v3->v4:
> Only '[PATCH v4 1/7] mfd: add syscon driver based on regmap' is changed.
> 
> Dong Aisheng (4):
>   mfd: add syscon driver based on regmap
>   ARM: imx6q: add iomuxc gpr support into syscon
>   regulator: anatop-regulator: convert to use syscon to access anatop
>     register
>   mfd: anatop-mfd: remove anatop driver
> 
>  Documentation/devicetree/bindings/mfd/syscon.txt |   20 ++
>  arch/arm/boot/dts/imx6q.dtsi                     |    9 +-
>  arch/arm/mach-imx/Kconfig                        |    2 +-
>  arch/arm/mach-imx/mach-imx6q.c                   |   47 ++--
>  drivers/mfd/Kconfig                              |   12 +-
>  drivers/mfd/Makefile                             |    2 +-
>  drivers/mfd/anatop-mfd.c                         |  124 ---------
>  drivers/mfd/syscon.c                             |  176 ++++++++++++
>  drivers/regulator/Kconfig                        |    2 +-
>  drivers/regulator/anatop-regulator.c             |   31 ++-
>  include/linux/mfd/anatop.h                       |   40 ---
>  include/linux/mfd/syscon.h                       |   23 ++
>  include/linux/mfd/syscon/imx6q-iomuxc-gpr.h      |  319 ++++++++++++++++++++++
>  13 files changed, 593 insertions(+), 214 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/mfd/syscon.txt
>  delete mode 100644 drivers/mfd/anatop-mfd.c
>  create mode 100644 drivers/mfd/syscon.c
>  delete mode 100644 include/linux/mfd/anatop.h
>  create mode 100644 include/linux/mfd/syscon.h
>  create mode 100644 include/linux/mfd/syscon/imx6q-iomuxc-gpr.h
> 
> 
--
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/