From: Rob Herring <robh@kernel.org>
To: Nina Wu <nina-cm.wu@mediatek.com>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
Zhen Lei <thunder.leizhen@huawei.com>,
Neal Liu <neal.liu@mediatek.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, srv_heupstream@mediatek.com,
Jackson-kt.Chang@mediatek.com
Subject: Re: [PATCH 1/2] dt-bindings: devapc: Update bindings
Date: Fri, 26 Mar 2021 13:58:02 -0600 [thread overview]
Message-ID: <20210326195802.GA3761703@robh.at.kernel.org> (raw)
In-Reply-To: <1616743871-8087-1-git-send-email-nina-cm.wu@mediatek.com>
On Fri, Mar 26, 2021 at 03:31:10PM +0800, Nina Wu wrote:
> From: Nina Wu <Nina-CM.Wu@mediatek.com>
>
> To support newer hardware architecture of devapc,
> update device tree bindings.
>
> Signed-off-by: Nina Wu <Nina-CM.Wu@mediatek.com>
> ---
> .../devicetree/bindings/soc/mediatek/devapc.yaml | 41 ++++++++++++++++++++++
> 1 file changed, 41 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/soc/mediatek/devapc.yaml b/Documentation/devicetree/bindings/soc/mediatek/devapc.yaml
> index 31e4d3c..489f6a9 100644
> --- a/Documentation/devicetree/bindings/soc/mediatek/devapc.yaml
> +++ b/Documentation/devicetree/bindings/soc/mediatek/devapc.yaml
> @@ -20,9 +20,27 @@ properties:
> compatible:
> enum:
> - mediatek,mt6779-devapc
> + - mediatek,mt8192-devapc
> +
> + version:
> + description: The version of the hardware architecture
This should be implied by the compatible string.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + enum: [1, 2]
> + maxItems: 1
> +
> + slave_type_num:
vendor prefix needed and s/_/-/
> + description: The number of the devapc set
What?
> + $ref: /schemas/types.yaml#/definitions/uint32
> + enum: [1, 4]
> + maxItems: 1
>
> reg:
> description: The base address of devapc register bank
> + maxItems: 4
Need to define what each region is.
> +
> + vio_idx_num:
vendor prefix needed and s/_/-/
> + description: The number of the devices controlled by devapc
No need to know which devices?
> + $ref: /schemas/types.yaml#/definitions/uint32-array
> maxItems: 1
uint32-array with 'maxItems: 1' is just 'uint32'
>
> interrupts:
> @@ -39,7 +57,10 @@ properties:
>
> required:
> - compatible
> + - version
> + - slave_type_num
> - reg
> + - vio_idx_num
> - interrupts
> - clocks
> - clock-names
> @@ -53,8 +74,28 @@ examples:
>
> devapc: devapc@10207000 {
> compatible = "mediatek,mt6779-devapc";
> + version = <1>;
> + slave_type_num = <1>;
> reg = <0x10207000 0x1000>;
> + vio_idx_num = <511>;
> interrupts = <GIC_SPI 168 IRQ_TYPE_LEVEL_LOW>;
> clocks = <&infracfg_ao CLK_INFRA_DEVICE_APC>;
> clock-names = "devapc-infra-clock";
> };
> + - |
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> + #include <dt-bindings/clock/mt8192-clk.h>
> +
> + devapc: devapc@10207000 {
> + compatible = "mediatek,mt8192-devapc";
> + version = <2>;
> + slave_type_num = <4>;
> + reg = <0 0x10207000 0 0x1000>,
> + <0 0x10274000 0 0x1000>,
> + <0 0x10275000 0 0x1000>,
> + <0 0x11020000 0 0x1000>;
> + vio_idx_num = <367 292 242 58>;
Is the length of this the same as the value of slave_type_num? If so,
don't need both.
> + interrupts = <GIC_SPI 187 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&infracfg_ao CLK_INFRA_DEVICE_APC>;
> + clock-names = "devapc-infra-clock";
> + };
> --
> 2.6.4
>
next prev parent reply other threads:[~2021-03-26 19:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 7:31 [PATCH 1/2] dt-bindings: devapc: Update bindings Nina Wu
2021-03-26 7:31 ` [PATCH 2/2] soc: mediatek: Add mt8192 devapc driver Nina Wu
2021-03-29 11:16 ` Matthias Brugger
2021-03-30 1:03 ` Nina Wu
2021-03-26 15:10 ` [PATCH 1/2] dt-bindings: devapc: Update bindings Rob Herring
2021-03-29 2:38 ` Nina Wu
2021-03-26 16:18 ` Chun-Kuang Hu
2021-03-29 2:43 ` Nina Wu
2021-03-26 19:58 ` Rob Herring [this message]
2021-03-29 3:22 ` Nina Wu
2021-03-29 11:16 ` Matthias Brugger
2021-03-30 1:06 ` Nina Wu
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=20210326195802.GA3761703@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=Jackson-kt.Chang@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=neal.liu@mediatek.com \
--cc=nina-cm.wu@mediatek.com \
--cc=srv_heupstream@mediatek.com \
--cc=thunder.leizhen@huawei.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: 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