LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: rishabhb@codeaurora.org To: Stephen Boyd <swboyd@chromium.org> Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm@lists.infradead.org, tsoni@codeaurora.org, ckadabi@codeaurora.org, evgreen@chromium.org, robh@kernel.org Subject: Re: [PATCH v6 1/2] dt-bindings: Documentation for qcom, llcc Date: Wed, 16 May 2018 10:33:14 -0700 [thread overview] Message-ID: <385198cbb91c4a36ad758997916ad271@codeaurora.org> (raw) In-Reply-To: <152649021310.210890.14841324536807182632@swboyd.mtv.corp.google.com> On 2018-05-16 10:03, Stephen Boyd wrote: > Quoting Rishabh Bhatnagar (2018-05-08 13:22:00) >> diff --git a/Documentation/devicetree/bindings/arm/msm/qcom,llcc.txt >> b/Documentation/devicetree/bindings/arm/msm/qcom,llcc.txt >> new file mode 100644 >> index 0000000..a586a17 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/arm/msm/qcom,llcc.txt >> @@ -0,0 +1,32 @@ >> +== Introduction== >> + >> +LLCC (Last Level Cache Controller) provides last level of cache >> memory in SOC, >> +that can be shared by multiple clients. Clients here are different >> cores in the >> +SOC, the idea is to minimize the local caches at the clients and >> migrate to >> +common pool of memory. Cache memory is divided into partitions called >> slices >> +which are assigned to clients. Clients can query the slice details, >> activate >> +and deactivate them. >> + >> +Properties: >> +- compatible: >> + Usage: required >> + Value type: <string> >> + Definition: must be "qcom,sdm845-llcc" >> + >> +- reg: >> + Usage: required >> + Value Type: <prop-encoded-array> >> + Definition: Start address and the range of the LLCC registers. > > Start address and size? > Yes i'll change it to Start address and size of the register region. >> + >> +- max-slices: >> + usage: required >> + Value Type: <u32> >> + Definition: Number of cache slices supported by hardware >> + >> +Example: >> + >> + llcc: qcom,llcc@1100000 { > > cache-controller@1100000 ? > We have tried to use consistent naming convention as in llcc_* everywhere. Using cache-controller will mix and match the naming convention. Also in the documentation it is explained what llcc is and its full form. >> + compatible = "qcom,sdm845-llcc"; >> + reg = <0x1100000 0x250000>; >> + max-slices = <32>; >> + }; >> --
next prev parent reply other threads:[~2018-05-16 17:33 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-05-08 20:21 [PATCH v6 0/2] SDM845 System Cache Driver Rishabh Bhatnagar 2018-05-08 20:22 ` [PATCH v6 1/2] dt-bindings: Documentation for qcom, llcc Rishabh Bhatnagar 2018-05-16 17:03 ` Stephen Boyd 2018-05-16 17:33 ` rishabhb [this message] 2018-05-16 18:08 ` Stephen Boyd 2018-05-16 23:32 ` rishabhb 2018-05-18 14:31 ` Rob Herring 2018-05-08 20:22 ` [PATCH v6 2/2] drivers: soc: Add LLCC driver Rishabh Bhatnagar 2018-05-10 20:15 ` Evan Green
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=385198cbb91c4a36ad758997916ad271@codeaurora.org \ --to=rishabhb@codeaurora.org \ --cc=ckadabi@codeaurora.org \ --cc=devicetree@vger.kernel.org \ --cc=evgreen@chromium.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-arm@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=robh@kernel.org \ --cc=swboyd@chromium.org \ --cc=tsoni@codeaurora.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).