From: Krzysztof Kozlowski <krzk@kernel.org>
To: Shun-yi Wang <shun-yi.wang@mediatek.com>,
Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh@kernel.org>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Conor Dooley <conor+dt@kernel.org>,
Tinghan Shen <tinghan.shen@mediatek.com>,
linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Project_Global_Chrome_Upstream_Group@mediatek.com,
jason-ch.chen@mediatek.com, yaya.chang@mediatek.com,
teddy.chen@mediatek.com
Subject: Re: [PATCH v2 1/2] dt-bindings: remoteproc: Support multiple reserved memory regions
Date: Wed, 31 Jul 2024 14:40:47 +0200 [thread overview]
Message-ID: <daadc099-4c07-4dda-9caa-662583629cde@kernel.org> (raw)
In-Reply-To: <20240731121730.1196-2-shun-yi.wang@mediatek.com>
On 31/07/2024 14:17, Shun-yi Wang wrote:
> From: "shun-yi.wang" <shun-yi.wang@mediatek.com>
>
> Remove the maximum number of 1 for memory regions.
Why?
> Instead, add some descriptions to ensure the integrity
> of the documentation.
What? How is this related?
>
> Signed-off-by: shun-yi.wang <shun-yi.wang@mediatek.com>
> ---
> Documentation/devicetree/bindings/remoteproc/mtk,scp.yaml | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/remoteproc/mtk,scp.yaml b/Documentation/devicetree/bindings/remoteproc/mtk,scp.yaml
> index d05d1563ec19..3362c8ffdccc 100644
> --- a/Documentation/devicetree/bindings/remoteproc/mtk,scp.yaml
> +++ b/Documentation/devicetree/bindings/remoteproc/mtk,scp.yaml
> @@ -55,7 +55,9 @@ properties:
> initializing SCP.
>
> memory-region:
> - maxItems: 1
No, no, no. Bindings must be specific/constrainted.
> + description:
> + List of phandles to the reserved memory nodes used by
> + remoteproc devices.
No, drop, it's entirely redundant and pointless. You did not add any new
information. This is always a list, always phandles and always reserved
memory regions. So what does it bring?
Please do not upstream random junk from your downstream kernel. :(
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-07-31 12:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 12:17 [PATCH v2 0/2] " Shun-yi Wang
2024-07-31 12:17 ` [PATCH v2 1/2] dt-bindings: remoteproc: " Shun-yi Wang
2024-07-31 12:40 ` Krzysztof Kozlowski [this message]
2024-07-31 13:41 ` Shun-Yi Wang (王順億)
2024-07-31 13:54 ` Krzysztof Kozlowski
2024-07-31 16:49 ` Krzysztof Kozlowski
2024-07-31 12:17 ` [PATCH v2 2/2] remoteproc: mediatek: " Shun-yi Wang
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=daadc099-4c07-4dda-9caa-662583629cde@kernel.org \
--to=krzk@kernel.org \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=andersson@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jason-ch.chen@mediatek.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=shun-yi.wang@mediatek.com \
--cc=teddy.chen@mediatek.com \
--cc=tinghan.shen@mediatek.com \
--cc=yaya.chang@mediatek.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
all inboxes | Powered by JetHome®