From: Hide Hako <opi5plus@bcc.bai.ne.jp>
To: Maud Spierings <maud_spierings@hotmail.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, heiko@sntech.de,
krzk+dt@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-sound@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v2] arm64: dts: rockchip: Enables sound output from the audio jack on OrangePI5 Plus
Date: Fri, 29 Aug 2025 20:59:57 +0900 [thread overview]
Message-ID: <0b061e42-0a01-4839-871c-a5d760dbddeb@bcc.bai.ne.jp> (raw)
In-Reply-To: <AM7P189MB1009A67370CA029038DF2A69E33BA@AM7P189MB1009.EURP189.PROD.OUTLOOK.COM>
Hello Maud,
On 2025/08/28 17:47, Maud Spierings wrote:
> I recommend rebasing on the latest next since my fix [1] was applied.
> I also recommend testing it with that patch, for me that fixed the
> headphone detection and enabled audio playback. The microphone is not
> working yet though.
>
> Link:
> https://lore.kernel.org/all/20250823-orangepi5-v1-1-ae77dd0e06d7@hotmail.com/
> [1]
>
Today, i build linux-next.
But sound not come out from headphone.
If you test the 6.17 kernel after using the 6.16 kernel, sound will be
output. Try building and testing in an environment with only the 6.17
kernel.
Or is it okay to use the JMB582 "M.2" nvme-sata 3.0 expansion card to
connect a 2.5-inch SSD?
This makes disk swapping easy and convenient.
Hide
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-08-29 15:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 13:44 [PATCH v2] arm64: dts: rockchip: Enables sound output from the audio jack on OrangePI5 Plus Hide Hako
2025-08-28 8:47 ` Maud Spierings
2025-08-29 11:59 ` Hide Hako [this message]
2025-08-29 12:09 ` Maud Spierings
2025-08-29 12:53 ` Hide Hako
2025-08-28 12:04 ` Heiko Stuebner
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=0b061e42-0a01-4839-871c-a5d760dbddeb@bcc.bai.ne.jp \
--to=opi5plus@bcc.bai.ne.jp \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-sound@vger.kernel.org \
--cc=maud_spierings@hotmail.com \
--cc=robh@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