From: Linus Walleij <linus.walleij@linaro.org>
To: Frank Wunderlich <frank-w@public-files.de>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Frank Wunderlich <linux@fw-web.de>,
linux-mediatek@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Sean Wang <sean.wang@kernel.org>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH v2] dt-bindings: pinctrl: update uart/mmc bindings for MT7986 SoC
Date: Tue, 8 Nov 2022 15:50:44 +0100 [thread overview]
Message-ID: <CACRpkdZFkeX7J9R2C0rhF+WZJXe65y6FfeBEMBGGkSTh4AWmsQ@mail.gmail.com> (raw)
In-Reply-To: <trinity-889b4468-8a50-4eae-80a1-6bd9ffbeaaf2-1667577856206@3c-app-gmx-bs24>
On Fri, Nov 4, 2022 at 5:04 PM Frank Wunderlich <frank-w@public-files.de> wrote:
> > Gesendet: Dienstag, 25. Oktober 2022 um 20:35 Uhr
> > Von: "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>
> > Betreff: Re: [PATCH v2] dt-bindings: pinctrl: update uart/mmc bindings for MT7986 SoC
> >
> > On 25/10/2022 03:02, Frank Wunderlich wrote:
> > > From: Frank Wunderlich <frank-w@public-files.de>
> > >
> > > Add new splitted uart pins and emmc_51
> > >
> > > Signed-off-by: Frank Wunderlich <frank-w@public-files.de>
> >
> >
> > Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>
> after talking with MTK for the emmc pinctrl settings (custom pull-up) they suggested me to change
> binding to fix other emmc-values and allow multiple (2) uart-items
>
> so on top of this patch
>
> then:
> properties:
> groups:
> - enum: [emmc, emmc_rst, emmc_51]
> + enum: [emmc_45, emmc_51]
> - if:
> properties:
> function:
> @@ -231,10 +231,12 @@ patternProperties:
> then:
> properties:
> groups:
> - enum: [uart1_0, uart1_rx_tx, uart1_cts_rts, uart1_1,
> - uart1_2_rx_tx, uart1_2_cts_rts, uart1_3_rx_tx,
> - uart1_3_cts_rts, uart2_0_rx_tx, uart2_0_cts_rts,
> - uart2_1, uart0, uart1, uart2]
> + items:
> + enum: [uart1_0, uart1_rx_tx, uart1_cts_rts, uart1_1,
> + uart1_2_rx_tx, uart1_2_cts_rts, uart1_3_rx_tx,
> + uart1_3_cts_rts, uart2_0_rx_tx, uart2_0_cts_rts,
> + uart2_1, uart0, uart1, uart2]
> + maxItems: 2
>
> i would squash these changes and send as v3 or should i send an extra-patch?
Squash and send av v3 if you haven't already! Easiest for me.
Yours,
Linus Walleij
next prev parent reply other threads:[~2022-11-08 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 7:02 [PATCH v2] dt-bindings: pinctrl: update uart/mmc bindings for MT7986 SoC Frank Wunderlich
2022-10-25 19:35 ` Krzysztof Kozlowski
2022-11-04 16:04 ` Aw: " Frank Wunderlich
2022-11-08 14:50 ` Linus Walleij [this message]
2022-11-08 14:57 ` Frank Wunderlich
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=CACRpkdZFkeX7J9R2C0rhF+WZJXe65y6FfeBEMBGGkSTh4AWmsQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=frank-w@public-files.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@fw-web.de \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sean.wang@kernel.org \
/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