public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Val Packett <val@packett.cool>
To: webgeek1234@gmail.com, Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, Teguh Sobirin <teguh@sobir.in>
Subject: Re: [PATCH v7 3/6] arm64: dts: qcom: Add AYN QCS8550 Common
Date: Thu, 30 Apr 2026 20:59:05 -0300	[thread overview]
Message-ID: <51eb35d3-5390-4f3b-9cb7-8d289151a650@packett.cool> (raw)
In-Reply-To: <20260430-ayn-qcs8550-v7-3-591a96735fa3@gmail.com>


On 4/30/26 3:43 PM, Aaron Kling via B4 Relay wrote:
> From: Teguh Sobirin <teguh@sobir.in>
>
> This contains everything common between the AYN QCS8550 devices. It will
> be included by device specific dts'.
> [..]
> +
> +	/* The tzlog label is required by ABL to apply a dtbo, but it can be on any node */
> +	qcom_tzlog: chosen {
> [..]
> +
> +	/* The arch_timer label is unused here, but is required by ABL to apply a dtbo */
> +	arch_timer: timer { };

awkwaaard.. Is there any problem with requiring erased dtbo? For phones 
that's generally what's done. Having junk from random dtbos is best avoided.

Also according to the pmOS wiki [1] at least on some of these devices, 
there's no need to boot from ABL at all! There's also U-Boot and you can 
switch between ABL and U-Boot at will (sounds awesome!)

> [..]
> +&i2c_hub_2 {
> +	clock-frequency = <400000>;
> +
> +	status = "okay";
> +
> +	spk_amp_l: amplifier@34 {
> +		compatible = "awinic,aw88166";
> +		reg = <0x34>;
> +		#sound-dai-cells = <0>;
> +		reset-gpios = <&tlmm 103 GPIO_ACTIVE_LOW>;
> +		awinic,audio-channel = <0>;
> +		awinic,sync-flag;
> +		sound-name-prefix = "SPK_L";
I guess there's no real standard/convention for the prefixes but maybe 
worth changing to the more readable "Amplifier L" / "Amplifier R" that's 
used on e.g. the fairphone,fp5?
> +	};
> +
> +	spk_amp_r: amplifier@35 {
> +		compatible = "awinic,aw88166";
> +		reg = <0x35>;
> +		#sound-dai-cells = <0>;
Also #sound-dai-cells should go last, with a newline before it.
> +		reset-gpios = <&tlmm 100 GPIO_ACTIVE_LOW>;
> +		awinic,audio-channel = <1>;
> +		awinic,sync-flag;
The awinic properties should also be a newline-separated "block", before 
the # one.
> +		sound-name-prefix = "SPK_R";
> +	};
> +};
> [..]

BTW, do these "just work" right now?

If so, I guess you're lucky and the "firmware" / register config binary 
for these devices configures a 16-bit 48kHz format which is the one the 
soc driver forces.. because the aw88166 driver, just like other awinic 
amp drivers, doesn't negotiate the format stuff at all and blatantly 
lies about supporting multiple formats :) I'm currently fixing this for 
aw88261[2] but eventually we'll probably need to actually kinda unify 
these drivers..

[1]: https://wiki.postmarketos.org/wiki/AYN_Thor_(ayn-thor)
[2]: https://lore.kernel.org/all/20260420213250.215465-2-val@packett.cool/


~val


  reply	other threads:[~2026-04-30 23:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-30 18:43 [PATCH v7 0/6] arm64: dts: qcom: Support AYN QCS8550 Devices Aaron Kling via B4 Relay
2026-04-30 18:43 ` [PATCH v7 1/6] dt-bindings: vendor-prefixes: Add AYN Technologies Aaron Kling via B4 Relay
2026-04-30 18:43 ` [PATCH v7 2/6] dt-bindings: arm: qcom: Add AYN QCS8550 Devices Aaron Kling via B4 Relay
2026-04-30 18:43 ` [PATCH v7 3/6] arm64: dts: qcom: Add AYN QCS8550 Common Aaron Kling via B4 Relay
2026-04-30 23:59   ` Val Packett [this message]
2026-05-01  1:14     ` Aaron Kling
2026-04-30 18:43 ` [PATCH v7 4/6] arm64: dts: qcom: Add AYN Odin 2 Mini Aaron Kling via B4 Relay
2026-04-30 18:43 ` [PATCH v7 5/6] arm64: dts: qcom: Add AYN Odin 2 Portal Aaron Kling via B4 Relay
2026-04-30 18:43 ` [PATCH v7 6/6] arm64: dts: qcom: Add AYN Thor Aaron Kling via B4 Relay

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=51eb35d3-5390-4f3b-9cb7-8d289151a650@packett.cool \
    --to=val@packett.cool \
    --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=robh@kernel.org \
    --cc=teguh@sobir.in \
    --cc=webgeek1234@gmail.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