From: Anup Patel <anup@brainfault.org> To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com> Cc: Daniel Lezcano <daniel.lezcano@linaro.org>, Thomas Gleixner <tglx@linutronix.de>, Guo Ren <guoren@linux.alibaba.com>, Bin Meng <bmeng.cn@gmail.com>, Xiang W <wxjstz@126.com>, Samuel Holland <samuel@sholland.org>, Atish Patra <atish.patra@wdc.com>, Rob Herring <robh+dt@kernel.org>, Palmer Dabbelt <palmer@dabbelt.com>, Paul Walmsley <paul.walmsley@sifive.com>, Anup Patel <anup.patel@wdc.com>, "linux-kernel@vger.kernel.org List" <linux-kernel@vger.kernel.org>, DTML <devicetree@vger.kernel.org>, linux-riscv <linux-riscv@lists.infradead.org>, OpenSBI <opensbi@lists.infradead.org> Subject: Re: [PATCH v2 1/1] dt-bindings: reg-io-width for SiFive CLINT Date: Mon, 18 Oct 2021 10:03:04 +0530 [thread overview] Message-ID: <CAAhSdy3JU6jitTWFk4CVRG5Xc7P7ueZzd=xmnKBNpx8eGaR6hw@mail.gmail.com> (raw) In-Reply-To: <20211015120735.27972-1-heinrich.schuchardt@canonical.com> On Fri, Oct 15, 2021 at 5:37 PM Heinrich Schuchardt <heinrich.schuchardt@canonical.com> wrote: > > The CLINT in the T-HEAD 9xx processors do not support 64bit mmio access to > the MTIMER device. The current schema does not allow to specify this. > > OpenSBI currently uses a property 'clint,has-no-64bit-mmio' to indicate the > restriction. Samuael Holland suggested in > lib: utils/timer: Use standard property to specify 32-bit I/O > https://github.com/smaeul/opensbi/commit/b95e9cf7cf93b0af16fc89204378bc59ff30008e > to use "reg-io-width = <4>;" as the reg-io-width property is generally used > in the devicetree schema for such a condition. > > A release candidate of the ACLINT specification is available at > https://github.com/riscv/riscv-aclint/releases > > Add reg-io-width as optional property to the SiFive Core Local Interruptor. > Add a new compatible string "allwinner,sun20i-d1-clint" for the CLINT of > the Allwinner D1 SoC. > > Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com> > --- > .../devicetree/bindings/timer/sifive,clint.yaml | 13 +++++++++++-- > 1 file changed, 11 insertions(+), 2 deletions(-) > > diff --git a/Documentation/devicetree/bindings/timer/sifive,clint.yaml b/Documentation/devicetree/bindings/timer/sifive,clint.yaml > index a35952f48742..d3b4c6844e2f 100644 > --- a/Documentation/devicetree/bindings/timer/sifive,clint.yaml > +++ b/Documentation/devicetree/bindings/timer/sifive,clint.yaml > @@ -26,6 +26,7 @@ properties: > - enum: > - sifive,fu540-c000-clint > - canaan,k210-clint > + - allwinner,sun20i-d1-clint > - const: sifive,clint0 > > description: > @@ -33,14 +34,22 @@ properties: > Supported compatible strings are - > "sifive,fu540-c000-clint" for the SiFive CLINT v0 as integrated > onto the SiFive FU540 chip, "canaan,k210-clint" for the SiFive > - CLINT v0 as integrated onto the Canaan Kendryte K210 chip, and > - "sifive,clint0" for the SiFive CLINT v0 IP block with no chip > + CLINT v0 as integrated onto the Canaan Kendryte K210 chip, > + "allwinner,sun20i-d1-clint" for the CLINT in the Allwinner D1 SoC, > + and "sifive,clint0" for the SiFive CLINT v0 IP block with no chip > integration tweaks. > Please refer to sifive-blocks-ip-versioning.txt for details > > reg: > maxItems: 1 > > + reg-io-width: > + description: | > + Some CLINT implementations, e.g. on the T-HEAD 9xx, only support > + 32bit access for MTIMER. > + $ref: /schemas/types.yaml#/definitions/uint32 > + const: 4 > + Please drop the "reg-io-width" DT property. Based on discussion on ACLINT MTIMER DT bindings, Rob suggested using implementation specific compatible string for detecting register IO width. We should follow the same strategy here as well. Regards, Anup > interrupts-extended: > minItems: 1 > > -- > 2.32.0 >
WARNING: multiple messages have this Message-ID (diff)
From: Anup Patel <anup@brainfault.org> To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com> Cc: Daniel Lezcano <daniel.lezcano@linaro.org>, Thomas Gleixner <tglx@linutronix.de>, Guo Ren <guoren@linux.alibaba.com>, Bin Meng <bmeng.cn@gmail.com>, Xiang W <wxjstz@126.com>, Samuel Holland <samuel@sholland.org>, Atish Patra <atish.patra@wdc.com>, Rob Herring <robh+dt@kernel.org>, Palmer Dabbelt <palmer@dabbelt.com>, Paul Walmsley <paul.walmsley@sifive.com>, Anup Patel <anup.patel@wdc.com>, "linux-kernel@vger.kernel.org List" <linux-kernel@vger.kernel.org>, DTML <devicetree@vger.kernel.org>, linux-riscv <linux-riscv@lists.infradead.org>, OpenSBI <opensbi@lists.infradead.org> Subject: Re: [PATCH v2 1/1] dt-bindings: reg-io-width for SiFive CLINT Date: Mon, 18 Oct 2021 10:03:04 +0530 [thread overview] Message-ID: <CAAhSdy3JU6jitTWFk4CVRG5Xc7P7ueZzd=xmnKBNpx8eGaR6hw@mail.gmail.com> (raw) In-Reply-To: <20211015120735.27972-1-heinrich.schuchardt@canonical.com> On Fri, Oct 15, 2021 at 5:37 PM Heinrich Schuchardt <heinrich.schuchardt@canonical.com> wrote: > > The CLINT in the T-HEAD 9xx processors do not support 64bit mmio access to > the MTIMER device. The current schema does not allow to specify this. > > OpenSBI currently uses a property 'clint,has-no-64bit-mmio' to indicate the > restriction. Samuael Holland suggested in > lib: utils/timer: Use standard property to specify 32-bit I/O > https://github.com/smaeul/opensbi/commit/b95e9cf7cf93b0af16fc89204378bc59ff30008e > to use "reg-io-width = <4>;" as the reg-io-width property is generally used > in the devicetree schema for such a condition. > > A release candidate of the ACLINT specification is available at > https://github.com/riscv/riscv-aclint/releases > > Add reg-io-width as optional property to the SiFive Core Local Interruptor. > Add a new compatible string "allwinner,sun20i-d1-clint" for the CLINT of > the Allwinner D1 SoC. > > Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com> > --- > .../devicetree/bindings/timer/sifive,clint.yaml | 13 +++++++++++-- > 1 file changed, 11 insertions(+), 2 deletions(-) > > diff --git a/Documentation/devicetree/bindings/timer/sifive,clint.yaml b/Documentation/devicetree/bindings/timer/sifive,clint.yaml > index a35952f48742..d3b4c6844e2f 100644 > --- a/Documentation/devicetree/bindings/timer/sifive,clint.yaml > +++ b/Documentation/devicetree/bindings/timer/sifive,clint.yaml > @@ -26,6 +26,7 @@ properties: > - enum: > - sifive,fu540-c000-clint > - canaan,k210-clint > + - allwinner,sun20i-d1-clint > - const: sifive,clint0 > > description: > @@ -33,14 +34,22 @@ properties: > Supported compatible strings are - > "sifive,fu540-c000-clint" for the SiFive CLINT v0 as integrated > onto the SiFive FU540 chip, "canaan,k210-clint" for the SiFive > - CLINT v0 as integrated onto the Canaan Kendryte K210 chip, and > - "sifive,clint0" for the SiFive CLINT v0 IP block with no chip > + CLINT v0 as integrated onto the Canaan Kendryte K210 chip, > + "allwinner,sun20i-d1-clint" for the CLINT in the Allwinner D1 SoC, > + and "sifive,clint0" for the SiFive CLINT v0 IP block with no chip > integration tweaks. > Please refer to sifive-blocks-ip-versioning.txt for details > > reg: > maxItems: 1 > > + reg-io-width: > + description: | > + Some CLINT implementations, e.g. on the T-HEAD 9xx, only support > + 32bit access for MTIMER. > + $ref: /schemas/types.yaml#/definitions/uint32 > + const: 4 > + Please drop the "reg-io-width" DT property. Based on discussion on ACLINT MTIMER DT bindings, Rob suggested using implementation specific compatible string for detecting register IO width. We should follow the same strategy here as well. Regards, Anup > interrupts-extended: > minItems: 1 > > -- > 2.32.0 > _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2021-10-18 4:33 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-15 12:07 [PATCH v2 1/1] dt-bindings: reg-io-width for SiFive CLINT Heinrich Schuchardt 2021-10-15 12:07 ` Heinrich Schuchardt 2021-10-18 4:33 ` Anup Patel [this message] 2021-10-18 4:33 ` Anup Patel 2021-10-18 7:30 ` Heinrich Schuchardt 2021-10-18 7:30 ` Heinrich Schuchardt
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='CAAhSdy3JU6jitTWFk4CVRG5Xc7P7ueZzd=xmnKBNpx8eGaR6hw@mail.gmail.com' \ --to=anup@brainfault.org \ --cc=anup.patel@wdc.com \ --cc=atish.patra@wdc.com \ --cc=bmeng.cn@gmail.com \ --cc=daniel.lezcano@linaro.org \ --cc=devicetree@vger.kernel.org \ --cc=guoren@linux.alibaba.com \ --cc=heinrich.schuchardt@canonical.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=opensbi@lists.infradead.org \ --cc=palmer@dabbelt.com \ --cc=paul.walmsley@sifive.com \ --cc=robh+dt@kernel.org \ --cc=samuel@sholland.org \ --cc=tglx@linutronix.de \ --cc=wxjstz@126.com \ /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 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.