From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Colin Cross <ccross@android.com>, Olof Johansson <olof@lixom.net>,
Thierry Reding <treding@nvidia.com>
Cc: Mohan Kumar <mkumard@nvidia.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the tegra tree
Date: Fri, 21 Jul 2023 13:07:30 +1000 [thread overview]
Message-ID: <20230721130730.058a385e@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 833 bytes --]
Hi all,
After merging the tegra tree, today's linux-next build (arm64 defconfig)
produced this warning:
arch/arm64/boot/dts/nvidia/tegra234-p3701.dtsi:57.27-60.10: Warning (graph_endpoint): /bus@0/aconnect@2900000/ahub@2900800/i2s@2901100/ports/port@1/endpoint: graph connection to node '/bus@0/i2c@31e0000/audio-codec@1c/port/endpoint' is not bidirectional
also defined at arch/arm64/boot/dts/nvidia/tegra234-p3737-0000.dtsi:14.30-17.10
arch/arm64/boot/dts/nvidia/tegra234-p3737-0000.dtsi:56.26-59.8: Warning (graph_endpoint): /bus@0/i2c@31e0000/audio-codec@1c/port/endpoint: graph connection to node '/bus@0/aconnect@2900000/ahub@2900800/i2s@2901000/ports/port@1/endpoint' is not bidirectional
Introduced by commit
89b143fbba40 ("arm64: tegra: Add audio support for IGX Orin")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-07-21 3:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 3:07 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-26 23:15 linux-next: build warning after merge of the tegra tree Stephen Rothwell
2022-06-27 11:53 ` Jon Hunter
2021-06-03 0:35 Stephen Rothwell
2021-06-03 2:01 ` Dmitry Osipenko
2021-06-03 12:18 ` Thierry Reding
2021-06-03 14:03 ` Dmitry Osipenko
2021-06-03 14:35 ` Thierry Reding
2021-06-03 14:37 ` Dmitry Osipenko
2015-05-07 4:06 Stephen Rothwell
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=20230721130730.058a385e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=ccross@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mkumard@nvidia.com \
--cc=olof@lixom.net \
--cc=treding@nvidia.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