[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOnJCUJ0fN5=+b4jDx+NPqUwgwGKuBNYt7d86dXYNyjzUYFAWQ@mail.gmail.com>
Date: Fri, 12 Jan 2024 15:50:15 -0800
From: Atish Patra <atishp@...shpatra.org>
To: Yu Chien Peter Lin <peterlin@...estech.com>
Cc: acme@...nel.org, adrian.hunter@...el.com, ajones@...tanamicro.com,
alexander.shishkin@...ux.intel.com, andre.przywara@....com,
anup@...infault.org, aou@...s.berkeley.edu, conor+dt@...nel.org,
conor.dooley@...rochip.com, conor@...nel.org, devicetree@...r.kernel.org,
dminus@...estech.com, evan@...osinc.com, geert+renesas@...der.be,
guoren@...nel.org, heiko@...ech.de, irogers@...gle.com,
jernej.skrabec@...il.com, jolsa@...nel.org, jszhang@...nel.org,
krzysztof.kozlowski+dt@...aro.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-perf-users@...r.kernel.org,
linux-renesas-soc@...r.kernel.org, linux-riscv@...ts.infradead.org,
linux-sunxi@...ts.linux.dev, locus84@...estech.com, magnus.damm@...il.com,
mark.rutland@....com, mingo@...hat.com, n.shubin@...ro.com,
namhyung@...nel.org, palmer@...belt.com, paul.walmsley@...ive.com,
peterz@...radead.org, prabhakar.mahadev-lad.rj@...renesas.com,
rdunlap@...radead.org, robh+dt@...nel.org, samuel@...lland.org,
sunilvl@...tanamicro.com, tglx@...utronix.de, tim609@...estech.com,
uwu@...nowy.me, wens@...e.org, will@...nel.org, ycliang@...estech.com,
inochiama@...look.com, chao.wei@...hgo.com, unicorn_wang@...look.com,
wefu@...hat.com
Subject: Re: [PATCH v7 04/16] dt-bindings: riscv: Add Andes interrupt
controller compatible string
On Tue, Jan 9, 2024 at 11:40 PM Yu Chien Peter Lin
<peterlin@...estech.com> wrote:
>
> Add "andestech,cpu-intc" compatible string to indicate that
> Andes specific local interrupt is supported on the core,
> e.g. AX45MP cores have 3 types of non-standard local interrupt
> which can be handled in supervisor mode:
>
PATCH1 in this series renames everything from ANDESTECH to ANDES to be
consistent.
Here you are adding DT binding with "andestech". Is there any
fundamental difference between these two to demand
this change ?
FYI: I don't mind either way as I don't have skin in the game. Just
something I noticed while reviewing the series.
> - Slave port ECC error interrupt
> - Bus write transaction error interrupt
> - Performance monitor overflow interrupt
>
> These interrupts are enabled/disabled via a custom register
> SLIE instead of the standard interrupt enable register SIE.
>
> Signed-off-by: Yu Chien Peter Lin <peterlin@...estech.com>
> Acked-by: Conor Dooley <conor.dooley@...rochip.com>
> Reviewed-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>
> ---
> Changes v1 -> v2:
> - New patch
> Changes v2 -> v3:
> - Updated commit message
> - Fixed possible compatibles for Andes INTC
> Changes v3 -> v4:
> - Add const entry instead of enum (Suggested by Conor)
> Changes v4 -> v5:
> - Include Conor's Acked-by
> - Include Prabhakar's Reviewed-by
> Changes v5 -> v6:
> - No change
> Changes v6 -> v7:
> - No change
> ---
> Documentation/devicetree/bindings/riscv/cpus.yaml | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/riscv/cpus.yaml b/Documentation/devicetree/bindings/riscv/cpus.yaml
> index 23646b684ea2..33c2b620a59f 100644
> --- a/Documentation/devicetree/bindings/riscv/cpus.yaml
> +++ b/Documentation/devicetree/bindings/riscv/cpus.yaml
> @@ -101,7 +101,11 @@ properties:
> const: 1
>
> compatible:
> - const: riscv,cpu-intc
> + oneOf:
> + - items:
> + - const: andestech,cpu-intc
> + - const: riscv,cpu-intc
> + - const: riscv,cpu-intc
>
> interrupt-controller: true
>
> --
> 2.34.1
>
--
Regards,
Atish
Powered by blists - more mailing lists