[PATCH V2 0/2] Add syscon name support

From: Orson Zhai
Date: Wed Nov 20 2019 - 10:45:42 EST


Hi,

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 from being compiled
in all-in-one image.

So I add syscons, syscon-names and an optional #vendor-cells property
as syscon consumer node's bindings. And implement coresponding helper
functions.

They have no side effect to current syscon consumer.

Thanks,
Orson

Changes in V2:

As per suggestion from Arnd:

* Remove #syscon-cells from syscon node.
* Add "#vendor-cells" into consumer node not affecting referred syscon
itself.
* Change helper funcions parameter accordingly.

-----
Orson Zhai (2):
dt-bindings: syscon: Add syscon-names to refer to syscon easily
mfd: syscon: Find syscon by names with arguments support

.../devicetree/bindings/mfd/syscon.txt | 43 +++++++++++
drivers/mfd/syscon.c | 75 +++++++++++++++++++
include/linux/mfd/syscon.h | 26 +++++++
3 files changed, 144 insertions(+)

--
2.18.0

________________________________
This email (including its attachments) is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. Unauthorized use, dissemination, distribution or copying of this email or the information herein or taking any action in reliance on the contents of this email or the information herein, by anyone other than the intended recipient, or an employee or agent responsible for delivering the message to the intended recipient, is strictly prohibited. If you are not the intended recipient, please do not read, copy, use or disclose any part of this e-mail to others. Please notify the sender immediately and permanently delete this e-mail and any attachments if you received it in error. Internet communications cannot be guaranteed to be timely, secure, error-free or virus-free. The sender does not accept liability for any errors or omissions.
æéäååéäåæäåæèïåæåäæäåæéïäåéçæéäææçåæääãäçéçææäçãåäãååæååæéäæåååãèéèçåæääïèåéèãååã äçææéæéäçääååãèèææéäïèäççäæäæåéæéäåææéäïåäååéäçæååååçåääãææäèäèçéäåæãååãæèæéæãåääåääéæåäææèäã