mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tinghan Shen <tinghan.shen@mediatek.com>
To: Zhiyong Tao <zhiyong.tao@mediatek.com>, <lee.jones@linaro.org>,
	<robh+dt@kernel.org>, <matthias.bgg@gmail.com>,
	<lgirdwood@gmail.com>, <broonie@kernel.org>,
	<eddie.huang@mediatek.com>, <a.zummo@towertech.it>,
	<alexandre.belloni@bootlin.com>, <fshao@chromium.org>
Cc: <srv_heupstream@mediatek.com>, <hui.liu@mediatek.com>,
	<hsin-hsiung.wang@mediatek.com>, <sean.wang@mediatek.com>,
	<macpaul.lin@mediatek.com>, <wen.su@mediatek.com>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-rtc@vger.kernel.org>,
	<Project_Global_Chrome_Upstream_Group@mediatek.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH v1 1/1] dt-bindings: pwrap: mediatek: fix pwrap document for mt8195
Date: Mon, 11 Apr 2022 10:51:40 +0800	[thread overview]
Message-ID: <8c27890e8b33bce333c2f8afaf4b4f893560ca7f.camel@mediatek.com> (raw)
In-Reply-To: <20220411014121.15015-2-zhiyong.tao@mediatek.com>

Hi all,

After discussed with Zhiyong, this patch will be sent together within mt8195 dts series.
It's because this change is related to mt8195 dts pwrap node.

Follow this link for resend version of this patch,

https://patchwork.kernel.org/project/linux-mediatek/patch/20220411022724.11005-2-tinghan.shen@mediatek.com/


Best regards,
Tinghan

On Mon, 2022-04-11 at 09:41 +0800, Zhiyong Tao wrote:
> From: "Zhiyong.Tao" <zhiyong.tao@mediatek.com>
> 
> fix pwrap document description for mt8195
> 
> Signed-off-by: Zhiyong.Tao <zhiyong.tao@mediatek.com>
> ---
>  .../devicetree/bindings/soc/mediatek/pwrap.txt         | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/soc/mediatek/pwrap.txt
> b/Documentation/devicetree/bindings/soc/mediatek/pwrap.txt
> index d74a7a5ae9f2..601647717ceb 100644
> --- a/Documentation/devicetree/bindings/soc/mediatek/pwrap.txt
> +++ b/Documentation/devicetree/bindings/soc/mediatek/pwrap.txt
> @@ -30,20 +30,20 @@ Required properties in pwrap device node.
>  	"mediatek,mt8195-pwrap" for MT8195 SoCs
>  	"mediatek,mt8516-pwrap" for MT8516 SoCs
>  - interrupts: IRQ for pwrap in SOC
> -- reg-names: Must include the following entries:
> +- reg-names: Must include "pwrap", "pwrap-bridge" is optinal.
>    "pwrap": Main registers base
>    "pwrap-bridge": bridge base (IP Pairing)
>  - reg: Must contain an entry for each entry in reg-names.
> -- reset-names: Must include the following entries:
> -  "pwrap"
> -  "pwrap-bridge" (IP Pairing)
> -- resets: Must contain an entry for each entry in reset-names.
>  - clock-names: Must include the following entries:
>    "spi": SPI bus clock
>    "wrap": Main module clock
>  - clocks: Must contain an entry for each entry in clock-names.
>  
>  Optional properities:
> +- reset-names: Some SoCs include the following entries:
> +  "pwrap"
> +  "pwrap-bridge" (IP Pairing)
> +- resets: Must contain an entry for each entry in reset-names.
>  - pmic: Using either MediaTek PMIC MFD as the child device of pwrap
>    See the following for child node definitions:
>    Documentation/devicetree/bindings/mfd/mt6397.txt


      reply	other threads:[~2022-04-11  2:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11  1:41 [PATCH v1 0/1] Mediatek PMIC patch Zhiyong Tao
2022-04-11  1:41 ` [PATCH v1 1/1] dt-bindings: pwrap: mediatek: fix pwrap document for mt8195 Zhiyong Tao
2022-04-11  2:51   ` Tinghan Shen [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=8c27890e8b33bce333c2f8afaf4b4f893560ca7f.camel@mediatek.com \
    --to=tinghan.shen@mediatek.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@bootlin.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=eddie.huang@mediatek.com \
    --cc=fshao@chromium.org \
    --cc=hsin-hsiung.wang@mediatek.com \
    --cc=hui.liu@mediatek.com \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=macpaul.lin@mediatek.com \
    --cc=matthias.bgg@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=sean.wang@mediatek.com \
    --cc=srv_heupstream@mediatek.com \
    --cc=wen.su@mediatek.com \
    --cc=zhiyong.tao@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®