From: <Conor.Dooley@microchip.com>
To: <robh@kernel.org>
Cc: <airlied@linux.ie>, <daniel@ffwll.ch>,
<krzysztof.kozlowski+dt@linaro.org>, <thierry.reding@gmail.com>,
<sam@ravnborg.org>, <Eugeniy.Paltsev@synopsys.com>,
<vkoul@kernel.org>, <lgirdwood@gmail.com>, <broonie@kernel.org>,
<fancer.lancer@gmail.com>, <daniel.lezcano@linaro.org>,
<palmer@dabbelt.com>, <palmer@rivosinc.com>,
<paul.walmsley@sifive.com>, <aou@eecs.berkeley.edu>,
<Conor.Dooley@microchip.com>, <masahiroy@kernel.org>,
<damien.lemoal@opensource.wdc.com>, <geert@linux-m68k.org>,
<niklas.cassel@wdc.com>, <dillon.minfei@gmail.com>,
<joabreu@synopsys.com>, <dri-devel@lists.freedesktop.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<dmaengine@vger.kernel.org>, <alsa-devel@alsa-project.org>,
<linux-riscv@lists.infradead.org>
Subject: Re: [PATCH v4 05/14] dt-bindings: memory-controllers: add canaan k210 sram controller
Date: Tue, 5 Jul 2022 19:28:05 +0000 [thread overview]
Message-ID: <d2369d3c-adfb-3158-2fa6-81c336502db9@microchip.com> (raw)
In-Reply-To: <20220705192307.GA2471961-robh@kernel.org>
On 05/07/2022 20:23, Rob Herring wrote:
> On Fri, Jul 01, 2022 at 08:22:51PM +0100, Conor Dooley wrote:
>> From: Conor Dooley <conor.dooley@microchip.com>
>>
>> The k210 U-Boot port has been using the clocks defined in the
>> devicetree to bring up the board's SRAM, but this violates the
>> dt-schema. As such, move the clocks to a dedicated node with
>> the same compatible string & document it.
>>
>> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
>> ---
>> .../memory-controllers/canaan,k210-sram.yaml | 52 +++++++++++++++++++
>> 1 file changed, 52 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/memory-controllers/canaan,k210-sram.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/memory-controllers/canaan,k210-sram.yaml b/Documentation/devicetree/bindings/memory-controllers/canaan,k210-sram.yaml
>> new file mode 100644
>> index 000000000000..82be32757713
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/memory-controllers/canaan,k210-sram.yaml
>> @@ -0,0 +1,52 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/memory-controllers/canaan,k210-sram.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Canaan K210 SRAM memory controller
>> +
>> +description: |
>
> Don't need '|'.
>
>> + The Canaan K210 SRAM memory controller is initialised and programmed by
>> + firmware, but an OS might want to read its registers for error reporting
>> + purposes and to learn about the DRAM topology.
>
> How the OS going to do that? You don't have any way defined to access
> the registers.
Eugh, copy paste. I'll rephrase in the respin. It should be "initialised by
firmware." There are no registers, only clocks.
>
> Also, where is the SRAM address itself defined?
The actual sram is in the memory node.
>
>> +
>> +maintainers:
>> + - Conor Dooley <conor@kernel.org>
>> +
>> +properties:
>> + compatible:
>> + enum:
>> + - canaan,k210-sram
>> +
>> + clocks:
>> + minItems: 1
>> + items:
>> + - description: sram0 clock
>> + - description: sram1 clock
>> + - description: aisram clock
>> +
>> + clock-names:
>> + minItems: 1
>> + items:
>> + - const: sram0
>> + - const: sram1
>> + - const: aisram
>> +
>> +required:
>> + - compatible
>> + - clocks
>> + - clock-names
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> + - |
>> + #include <dt-bindings/clock/k210-clk.h>
>> + memory-controller {
>> + compatible = "canaan,k210-sram";
>> + clocks = <&sysclk K210_CLK_SRAM0>,
>> + <&sysclk K210_CLK_SRAM1>,
>> + <&sysclk K210_CLK_AI>;
>> + clock-names = "sram0", "sram1", "aisram";
>> + };
>> --
>> 2.37.0
>>
>>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-07-05 19:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 19:22 [PATCH v4 00/14] Canaan devicetree fixes Conor Dooley
2022-07-01 19:22 ` [PATCH v4 01/14] dt-bindings: display: convert ilitek,ili9341.txt to dt-schema Conor Dooley
2022-07-01 19:22 ` [PATCH v4 02/14] dt-bindings: display: ili9341: document canaan kd233's lcd Conor Dooley
2022-07-05 19:04 ` Rob Herring
2022-07-01 19:22 ` [PATCH v4 03/14] ASoC: dt-bindings: convert designware-i2s to dt-schema Conor Dooley
2022-07-01 19:22 ` [PATCH v4 04/14] dt-bindings: dma: dw-axi-dmac: extend the number of interrupts Conor Dooley
2022-07-05 12:46 ` Vinod Koul
2022-07-05 12:50 ` Conor.Dooley
2022-07-01 19:22 ` [PATCH v4 05/14] dt-bindings: memory-controllers: add canaan k210 sram controller Conor Dooley
2022-07-05 19:23 ` Rob Herring
2022-07-05 19:28 ` Conor.Dooley [this message]
2022-07-05 19:31 ` Conor.Dooley
2022-07-01 19:22 ` [PATCH v4 06/14] riscv: dts: canaan: fix the k210's memory node Conor Dooley
2022-07-01 19:22 ` [PATCH v4 07/14] riscv: dts: canaan: fix the k210's timer nodes Conor Dooley
2022-07-01 19:22 ` [PATCH v4 08/14] riscv: dts: canaan: fix mmc node names Conor Dooley
2022-07-01 19:22 ` [PATCH v4 09/14] riscv: dts: canaan: fix kd233 display spi frequency Conor Dooley
2022-07-01 19:22 ` [PATCH v4 10/14] riscv: dts: canaan: use custom compatible for k210 i2s Conor Dooley
2022-07-01 19:22 ` [PATCH v4 11/14] riscv: dts: canaan: remove spi-max-frequency from controllers Conor Dooley
2022-07-01 19:22 ` [PATCH v4 12/14] riscv: dts: canaan: fix bus {ranges,reg} warnings Conor Dooley
2022-07-01 19:22 ` [PATCH v4 13/14] riscv: dts: canaan: add specific compatible for kd233's LCD Conor Dooley
2022-07-01 19:23 ` [PATCH v4 14/14] riscv: dts: canaan: build all devicetress if SOC_CANAAN Conor Dooley
2022-07-04 15:57 ` (subset) [PATCH v4 00/14] Canaan devicetree fixes Mark Brown
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=d2369d3c-adfb-3158-2fa6-81c336502db9@microchip.com \
--to=conor.dooley@microchip.com \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=airlied@linux.ie \
--cc=alsa-devel@alsa-project.org \
--cc=aou@eecs.berkeley.edu \
--cc=broonie@kernel.org \
--cc=damien.lemoal@opensource.wdc.com \
--cc=daniel.lezcano@linaro.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dillon.minfei@gmail.com \
--cc=dmaengine@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=fancer.lancer@gmail.com \
--cc=geert@linux-m68k.org \
--cc=joabreu@synopsys.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=masahiroy@kernel.org \
--cc=niklas.cassel@wdc.com \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=sam@ravnborg.org \
--cc=thierry.reding@gmail.com \
--cc=vkoul@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 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).