public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Adam <adamp@posteo.de>
To: Stephan Gerhold <stephan.gerhold@linaro.org>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org,
	~postmarketos/upstreaming@lists.sr.ht,
	phone-devel@vger.kernel.org
Subject: Re: [PATCH v4 3/3] arm64: dts: qcom: msm8916-wiko-chuppito: add initial devicetree
Date: Wed, 11 Mar 2026 18:40:29 +0000	[thread overview]
Message-ID: <abG3G3MQeKd3UAaL@MyryksLaptop> (raw)
In-Reply-To: <aa9Epb7MQ0qVFWGO@linaro.org>

On 26/03/09 11:07, Stephan Gerhold wrote:
> On Mon, Mar 09, 2026 at 09:48:12PM +0000, Paul Adam wrote:
> > On 26/03/09 10:16, Stephan Gerhold wrote:
> > > > diff --git a/arch/arm64/boot/dts/qcom/msm8916-wiko-chuppito.dts b/arch/arm64/boot/dts/qcom/msm8916-wiko-chuppito.dts
> > > > new file mode 100644
> > > > index 000000000000..d927bae2b208
> > > > --- /dev/null
> > > > +++ b/arch/arm64/boot/dts/qcom/msm8916-wiko-chuppito.dts
> > > > @@ -0,0 +1,315 @@
> > > > [...]
> > > > +&sound {
> > > > +	audio-routing = "AMIC1", "MIC BIAS Internal1",
> > > > +		"AMIC2", "MIC BIAS Internal2",
> > > > +		"AMIC3", "MIC BIAS Internal1";
> > > 
> > > Sorry, just noticed this now:
> > > 
> > > This seems a bit suspicious (I would expect "MIC BIAS Internal3"), have
> > > you tested if the secondary microphone works?
> > > 
> > > Thanks,
> > > Stephan
> > 
> > The secondary microphone does not work yet, neither with Internal1
> > nor Internal3.
> > 
> > In the downstream devicetree its Internal1 for AMIC3.
> > 
> > Is there a way for me to check which one is correct?
> > 
> 
> To be absolutely sure, only with the schematic diagram of the board...
> 
> Another option would be that the secondary microphone simply does not
> exist at all (i.e. there is only one microphone). Any idea if it works
> on Android?
> 
> If in doubt, it would be better to remove the line for AMIC3.
> 
> Thanks,
> Stephan

Tried around some more and got the secondary microphone to record something,
even without the third line. Will take the line out.

Paul

      parent reply	other threads:[~2026-03-11 18:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-07 17:23 [PATCH v4 0/3] Add wiko-chuppito devictree Paul Adam via B4 Relay
2026-03-07 17:23 ` [PATCH v4 1/3] dt-bindings: vendor-prefixes: add WIKO SAS Paul Adam via B4 Relay
2026-03-07 17:23 ` [PATCH v4 2/3] dt-bindings: arm: qcom: add wiko,chuppito compatible string Paul Adam via B4 Relay
2026-03-07 17:23 ` [PATCH v4 3/3] arm64: dts: qcom: msm8916-wiko-chuppito: add initial devicetree Paul Adam via B4 Relay
2026-03-09  9:16   ` Stephan Gerhold
2026-03-09 21:48     ` Paul Adam
2026-03-09 22:07       ` Stephan Gerhold
2026-03-10 12:30         ` Konrad Dybcio
2026-03-11 18:40         ` Paul Adam [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=abG3G3MQeKd3UAaL@MyryksLaptop \
    --to=adamp@posteo.de \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phone-devel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=stephan.gerhold@linaro.org \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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