From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andy Gross <agross@kernel.org>, Abel Vesa <abel.vesa@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Stephan Gerhold <stephan.gerhold@linaro.org>
Subject: Re: linux-next: manual merge of the usb tree with the qcom tree
Date: Wed, 8 Jan 2025 13:13:07 +0100 [thread overview]
Message-ID: <2025010801-easiest-excitable-a3ca@gregkh> (raw)
In-Reply-To: <20250106151712.4cf70651@canb.auug.org.au>
On Mon, Jan 06, 2025 at 03:17:12PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the usb tree got a conflict in:
>
> arch/arm64/boot/dts/qcom/x1e80100-qcp.dts
>
> between commit:
>
> ab8f487d2f89 ("arm64: dts: qcom: x1e80100-qcp: Enable SD card support")
>
> from the qcom tree and commit:
>
> 42943457e49d ("arm64: dts: qcom: x1e80100-qcp: Add FSUSB42 USB switches")
>
> from the usb tree.
>
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
>
> --
> Cheers,
> Stephen Rothwell
>
> diff --cc arch/arm64/boot/dts/qcom/x1e80100-qcp.dts
> index 9a7b45066be2,f45df1396eae..000000000000
> --- a/arch/arm64/boot/dts/qcom/x1e80100-qcp.dts
> +++ b/arch/arm64/boot/dts/qcom/x1e80100-qcp.dts
> @@@ -943,13 -977,79 +1048,86 @@@
> };
> };
>
> + sdc2_card_det_n: sdc2-card-det-state {
> + pins = "gpio71";
> + function = "gpio";
> + drive-strength = <2>;
> + bias-pull-up;
> + };
> +
> + usb_1_ss0_sbu_default: usb-1-ss0-sbu-state {
> + mode-pins {
> + pins = "gpio166";
> + function = "gpio";
> + bias-disable;
> + drive-strength = <2>;
> + output-high;
> + };
> +
> + oe-n-pins {
> + pins = "gpio168";
> + function = "gpio";
> + bias-disable;
> + drive-strength = <2>;
> + };
> +
> + sel-pins {
> + pins = "gpio167";
> + function = "gpio";
> + bias-disable;
> + drive-strength = <2>;
> + };
> +
> + };
> +
> + usb_1_ss1_sbu_default: usb-1-ss1-sbu-state {
> + mode-pins {
> + pins = "gpio177";
> + function = "gpio";
> + bias-disable;
> + drive-strength = <2>;
> + output-high;
> + };
> +
> + oe-n-pins {
> + pins = "gpio179";
> + function = "gpio";
> + bias-disable;
> + drive-strength = <2>;
> + };
> +
> + sel-pins {
> + pins = "gpio178";
> + function = "gpio";
> + bias-disable;
> + drive-strength = <2>;
> + };
> + };
> +
> + usb_1_ss2_sbu_default: usb-1-ss2-sbu-state {
> + mode-pins {
> + pins = "gpio169";
> + function = "gpio";
> + bias-disable;
> + drive-strength = <2>;
> + output-high;
> + };
> +
> + oe-n-pins {
> + pins = "gpio171";
> + function = "gpio";
> + bias-disable;
> + drive-strength = <2>;
> + };
> +
> + sel-pins {
> + pins = "gpio170";
> + function = "gpio";
> + bias-disable;
> + drive-strength = <2>;
> + };
> + };
> +
> wcd_default: wcd-reset-n-active-state {
> pins = "gpio191";
> function = "gpio";
Resolution looks good, thanks!
greg k-h
next prev parent reply other threads:[~2025-01-08 12:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 4:17 linux-next: manual merge of the usb tree with the qcom tree Stephen Rothwell
2025-01-08 12:13 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-14 1:40 Stephen Rothwell
2023-02-14 6:46 ` Greg KH
2023-02-21 9:43 ` Geert Uytterhoeven
2022-02-21 19:16 broonie
2022-02-22 7:44 ` Greg KH
2022-02-10 3:11 Stephen Rothwell
2022-02-10 8:02 ` Greg KH
2022-03-18 7:37 ` Stephen Rothwell
2021-09-21 2:30 Stephen Rothwell
2021-09-21 13:12 ` Bjorn Andersson
2021-09-21 13:16 ` Greg KH
2021-09-21 13:28 ` Bjorn Andersson
2021-08-06 14:13 Mark Brown
2021-08-06 14:09 Mark Brown
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=2025010801-easiest-excitable-a3ca@gregkh \
--to=greg@kroah.com \
--cc=abel.vesa@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=stephan.gerhold@linaro.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;
as well as URLs for NNTP newsgroup(s).