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 v3 1/7] dt-bindings: devapc: Add 'vio-idx-num' field to support mt8192
Date: Mon, 12 Apr 2021 10:59:10 -0500 [thread overview]
Message-ID: <20210412155910.GA3966290@robh.at.kernel.org> (raw)
In-Reply-To: <1617956377-4075-1-git-send-email-nina-cm.wu@mediatek.com>
On Fri, Apr 09, 2021 at 04:19:31PM +0800, Nina Wu wrote:
> From: Nina Wu <Nina-CM.Wu@mediatek.com>
>
> For new ICs, there are multiple devapc HWs for different subsys.
> We add a field 'vio-idx-num' in DT to indicate the number of
> devices controlled by each devapc.
> To be backward compatible with old ICs which have only one devapc
> HW, this field is not required. The 'vio-idx-num' info will be set
> in compatible data instead.
>
> Signed-off-by: Nina Wu <Nina-CM.Wu@mediatek.com>
> ---
> Documentation/devicetree/bindings/soc/mediatek/devapc.yaml | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/soc/mediatek/devapc.yaml b/Documentation/devicetree/bindings/soc/mediatek/devapc.yaml
> index 31e4d3c..909e524 100644
> --- a/Documentation/devicetree/bindings/soc/mediatek/devapc.yaml
> +++ b/Documentation/devicetree/bindings/soc/mediatek/devapc.yaml
> @@ -20,11 +20,17 @@ properties:
> compatible:
> enum:
> - mediatek,mt6779-devapc
> + - mediatek,mt8192-devapc
>
> reg:
> description: The base address of devapc register bank
> maxItems: 1
>
> + mediatek,vio-idx-num:
> + description: The number of the devices controlled by devapc
> + $ref: /schemas/types.yaml#/definitions/uint32
> + maxItems: 1
A uint32 is always 1 item, so drop. With that,
Reviewed-by: Rob Herring <robh@kernel.org>
> +
> interrupts:
> description: A single interrupt specifier
> maxItems: 1
> --
> 2.6.4
>
prev parent reply other threads:[~2021-04-12 15:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 8:19 [PATCH v3 1/7] dt-bindings: devapc: Add 'vio-idx-num' field to support mt8192 Nina Wu
2021-04-09 8:19 ` [PATCH v3 2/7] soc: mediatek: devapc: get 'vio_idx_num' info from DT Nina Wu
2021-04-09 8:19 ` [PATCH v3 3/7] soc: mediatek: devapc: add shared flag to IRQ Nina Wu
2021-04-09 8:19 ` [PATCH v3 4/7] soc: mediatek: devapc: rename register variable infra_base Nina Wu
2021-04-09 8:19 ` [PATCH v3 5/7] soc: mediatek: devapc: add debug register for new IC support Nina Wu
2021-04-09 8:19 ` [PATCH v3 6/7] soc: mediatek: devapc: support mt8192 Nina Wu
2021-04-09 8:19 ` [PATCH v3 7/7] arm64: dts: mt8192: Add devapc node Nina Wu
2021-04-12 15:59 ` Rob Herring [this message]
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=20210412155910.GA3966290@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;
as well as URLs for NNTP newsgroup(s).