From: Chris Brandt <Chris.Brandt@renesas.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-clk <linux-clk@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS
<devicetree@vger.kernel.org>,
Linux-Renesas" <linux-renesas-soc@vger.kernel.org>,
Simon Horman <horms+renesas@verge.net.au>
Subject: RE: [PATCH v3] clk: renesas: cpg-mssr: Add R7S9210 support
Date: Wed, 5 Sep 2018 15:31:56 +0000 [thread overview]
Message-ID: <TYXPR01MB1568EA45A14A2E811546ED2A8A020@TYXPR01MB1568.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <CAMuHMdUojvTWiGhULtp=tgTz56S2MAuYnT1p-JQWBn3PUag8jg@mail.gmail.com>
Hi Geert,
On Wednesday, September 05, 2018 1, Geert Uytterhoeven wrote:
> > So....I guess I didn't really have an issue after all.
>
> You do want to:
> 1. Document the two register ranges in the DT bindings,
> 2. Update the driver to map both ranges on RZ/A2.
The driver does not need to be updated.
Given this mapping:
cpg: clock-controller@fcfe0020 {
compatible = "renesas,r7s9210-cpg-mssr";
reg = <0xfcfe0010 0x455>; /* FCFE0010 - FCFE0465 */
clocks = <&extal_clk>;
clock-names = "extal";
#clock-cells = <2>;
#power-domain-cells = <0>;
#reset-cells = <1>;
};
This covers all the CPG, MSTP, power down and reset registers.
So I'm just going to map them all at once.
And, you can see that some CPG and MSTP register are mixed together.
Here is the list of registers in address order:
FRQCR FCFE_0010 (CPG)
STBCR1 FCFE_0020 (MSTP)
STBCR2 FCFE_0024 (MSTP)
CKIOSEL FCFE_0100 (CPG)
SCLKSEL FCFE_0104 (CPG)
STBCR3 FCFE_0420 (MSTP)
STBCR4 FCFE_0424 (MSTP)
STBCR5 FCFE_0428 (MSTP)
STBCR6 FCFE_042C (MSTP)
STBCR7 FCFE_0430 (MSTP)
STBCR8 FCFE_0434 (MSTP)
STBCR9 FCFE_0438 (MSTP)
STBCR10 FCFE_043C (MSTP)
SWRSTCR1 FCFE_0460 (RESET)
SWRSTCR2 FCFE_0464 (RESET)
etc...
So this should be all one memory block in this driver.
When you get to FCFF_C000+, that's where the 'specialty' registers are.
I think FCFF_C000+ should be a separate block, maybe in a separate driver.
Chris
WARNING: multiple messages have this Message-ID (diff)
From: Chris Brandt <Chris.Brandt@renesas.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-clk <linux-clk@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Simon Horman <horms+renesas@verge.net.au>
Subject: RE: [PATCH v3] clk: renesas: cpg-mssr: Add R7S9210 support
Date: Wed, 5 Sep 2018 15:31:56 +0000 [thread overview]
Message-ID: <TYXPR01MB1568EA45A14A2E811546ED2A8A020@TYXPR01MB1568.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <CAMuHMdUojvTWiGhULtp=tgTz56S2MAuYnT1p-JQWBn3PUag8jg@mail.gmail.com>
SGkgR2VlcnQsDQoNCk9uIFdlZG5lc2RheSwgU2VwdGVtYmVyIDA1LCAyMDE4IDEsIEdlZXJ0IFV5
dHRlcmhvZXZlbiB3cm90ZToNCj4gPiBTby4uLi5JIGd1ZXNzIEkgZGlkbid0IHJlYWxseSBoYXZl
IGFuIGlzc3VlIGFmdGVyIGFsbC4NCj4gDQo+IFlvdSBkbyB3YW50IHRvOg0KPiAgIDEuIERvY3Vt
ZW50IHRoZSB0d28gcmVnaXN0ZXIgcmFuZ2VzIGluIHRoZSBEVCBiaW5kaW5ncywNCj4gICAyLiBV
cGRhdGUgdGhlIGRyaXZlciB0byBtYXAgYm90aCByYW5nZXMgb24gUlovQTIuDQoNClRoZSBkcml2
ZXIgZG9lcyBub3QgbmVlZCB0byBiZSB1cGRhdGVkLg0KDQpHaXZlbiB0aGlzIG1hcHBpbmc6DQoN
CgljcGc6IGNsb2NrLWNvbnRyb2xsZXJAZmNmZTAwMjAgew0KCQljb21wYXRpYmxlID0gInJlbmVz
YXMscjdzOTIxMC1jcGctbXNzciI7DQoJCXJlZyA9IDwweGZjZmUwMDEwIDB4NDU1PjsgIC8qIEZD
RkUwMDEwIC0gRkNGRTA0NjUgKi8NCgkJY2xvY2tzID0gPCZleHRhbF9jbGs+Ow0KCQljbG9jay1u
YW1lcyA9ICJleHRhbCI7DQoJCSNjbG9jay1jZWxscyA9IDwyPjsNCgkJI3Bvd2VyLWRvbWFpbi1j
ZWxscyA9IDwwPjsNCgkJI3Jlc2V0LWNlbGxzID0gPDE+Ow0KCX07DQoNClRoaXMgY292ZXJzIGFs
bCB0aGUgQ1BHLCBNU1RQLCBwb3dlciBkb3duIGFuZCByZXNldCByZWdpc3RlcnMuDQoNClNvIEkn
bSBqdXN0IGdvaW5nIHRvIG1hcCB0aGVtIGFsbCBhdCBvbmNlLg0KDQpBbmQsIHlvdSBjYW4gc2Vl
IHRoYXQgc29tZSBDUEcgYW5kIE1TVFAgcmVnaXN0ZXIgYXJlIG1peGVkIHRvZ2V0aGVyLg0KSGVy
ZSBpcyB0aGUgbGlzdCBvZiByZWdpc3RlcnMgaW4gYWRkcmVzcyBvcmRlcjoNCg0KIEZSUUNSICAg
RkNGRV8wMDEwICAoQ1BHKQ0KU1RCQ1IxICAgRkNGRV8wMDIwICAoTVNUUCkNClNUQkNSMiAgIEZD
RkVfMDAyNCAgKE1TVFApDQpDS0lPU0VMICBGQ0ZFXzAxMDAgIChDUEcpDQpTQ0xLU0VMICBGQ0ZF
XzAxMDQgIChDUEcpDQpTVEJDUjMgICBGQ0ZFXzA0MjAgIChNU1RQKQ0KU1RCQ1I0ICAgRkNGRV8w
NDI0ICAoTVNUUCkNClNUQkNSNSAgIEZDRkVfMDQyOCAgKE1TVFApDQpTVEJDUjYgICBGQ0ZFXzA0
MkMgIChNU1RQKQ0KU1RCQ1I3ICAgRkNGRV8wNDMwICAoTVNUUCkNClNUQkNSOCAgIEZDRkVfMDQz
NCAgKE1TVFApDQpTVEJDUjkgICBGQ0ZFXzA0MzggIChNU1RQKQ0KU1RCQ1IxMCAgRkNGRV8wNDND
ICAoTVNUUCkNClNXUlNUQ1IxIEZDRkVfMDQ2MCAgKFJFU0VUKQ0KU1dSU1RDUjIgRkNGRV8wNDY0
ICAoUkVTRVQpDQogIGV0Yy4uLg0KDQpTbyB0aGlzIHNob3VsZCBiZSBhbGwgb25lIG1lbW9yeSBi
bG9jayBpbiB0aGlzIGRyaXZlci4NCg0KV2hlbiB5b3UgZ2V0IHRvIEZDRkZfQzAwMCssIHRoYXQn
cyB3aGVyZSB0aGUgJ3NwZWNpYWx0eScgcmVnaXN0ZXJzIGFyZS4gDQpJIHRoaW5rIEZDRkZfQzAw
MCsgc2hvdWxkIGJlIGEgc2VwYXJhdGUgYmxvY2ssIG1heWJlIGluIGEgc2VwYXJhdGUgZHJpdmVy
Lg0KDQoNCkNocmlzDQoNCg==
next prev parent reply other threads:[~2018-09-05 15:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 13:28 [PATCH v3] clk: renesas: cpg-mssr: Add R7S9210 support Chris Brandt
2018-09-05 14:12 ` Chris Brandt
2018-09-05 14:12 ` Chris Brandt
2018-09-05 14:31 ` Geert Uytterhoeven
2018-09-05 15:02 ` Chris Brandt
2018-09-05 15:02 ` Chris Brandt
2018-09-05 15:02 ` Chris Brandt
2018-09-05 15:07 ` Geert Uytterhoeven
2018-09-05 15:31 ` Chris Brandt [this message]
2018-09-05 15:31 ` Chris Brandt
2018-09-05 15:31 ` Chris Brandt
2018-09-06 11:55 ` Geert Uytterhoeven
2018-09-06 14:31 ` Chris Brandt
2018-09-06 14:31 ` Chris Brandt
2018-09-06 14:31 ` Chris Brandt
2018-09-10 13:18 ` Geert Uytterhoeven
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=TYXPR01MB1568EA45A14A2E811546ED2A8A020@TYXPR01MB1568.jpnprd01.prod.outlook.com \
--to=chris.brandt@renesas.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-clk@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.