linux-kernel - [PATCH 0/2] Add syscon name and #cells support

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-next>] [day] [month] [year] [list]

Message-ID: <20191114114525.12675-1-orson.zhai@unisoc.com>
Date:   Thu, 14 Nov 2019 19:45:23 +0800
From:   Orson Zhai <orson.zhai@...soc.com>
To:     Lee Jones <lee.jones@...aro.org>, Rob Herring <robh+dt@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        Arnd Bergmann <arnd@...db.de>
CC:     <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <steven.tang@...soc.com>, Orson Zhai <orson.zhai@...soc.com>
Subject: [PATCH 0/2] Add syscon name and #cells support

Our SoCs have a lot of glabal registers which is hard to be managed in 
current syscon structure.

Same register's offset is different in different SoCs. We used chip
config macro to manage them which prevents driver to be compiled in
all-in-one image.

After talking with Arnd and Rob at Linaro Connect 2017, I got the
idea to extend syscon with #cells support. And furthe, I added syscon
names support to help access multiple syscon nodes more easier.

These patches has been tested in our internal tree about 2 years.

They have no side effect to current syscon consumer.

Thanks,
Orson

--------------------
Orson Zhai (2):
  dt-bindings: Add syscon-names support
  mfd: syscon: Add syscon-names and phandle args support

 .../devicetree/bindings/mfd/syscon.txt        | 36 ++++++++++
 drivers/mfd/syscon.c                          | 65 +++++++++++++++++++
 include/linux/mfd/syscon.h                    | 22 +++++++
 3 files changed, 123 insertions(+)

-- 
2.18.0