From: "Martin Povišer" <povik@cutebit.org> To: Mark Brown <broonie@kernel.org> Cc: "Martin Povišer" <povik+lin@cutebit.org>, "Liam Girdwood" <lgirdwood@gmail.com>, "Rob Herring" <robh+dt@kernel.org>, "Krzysztof Kozlowski" <krzk+dt@kernel.org>, "Jaroslav Kysela" <perex@perex.cz>, "Takashi Iwai" <tiwai@suse.com>, alsa-devel@alsa-project.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, "Mark Kettenis" <kettenis@openbsd.org>, "Hector Martin" <marcan@marcan.st>, "Sven Peter" <sven@svenpeter.dev> Subject: Re: [RFC PATCH 0/5] Apple Macs machine-level ASoC driver Date: Fri, 22 Apr 2022 15:59:25 +0200 [thread overview] Message-ID: <0E735637-EDA8-4A68-8B43-01BCEC41245C@cutebit.org> (raw) In-Reply-To: <YmKoXbh04ZEs3dSZ@sirena.org.uk> > On 22. 4. 2022, at 15:06, Mark Brown <broonie@kernel.org> wrote: > > On Fri, Apr 22, 2022 at 02:53:54PM +0200, Martin Povišer wrote: > >>> Oh, I see - the speaker actually allows configuration of the slots >>> independently. Usually the left/right thing on mono devices only does >>> something for I2S where the bus clocking enforces that there be both >>> left and right channels. Either configuration is fine by me TBH, if you >>> can do that then you could just keep them mapped to the same channel >>> then mark the control as disabled since it should have no effect. > >> Well but is there some established way to mark a control as disabled? > > snd_ctl_activate_id(). Ha! Great. >> Another issue here is that if I disable it I can’t leave the routing >> control in it’s default value, which is ‘I2C Offset’ and makes the speaker >> amp ignore the slot mapping. > > Sure, that's fine - if a control genuinely has no effect it's fine to > hide it from userspace. The issue is where it's just that you don't see > the use, if the control demonstrably does nothing then that's fine. So I assume I can set the control from the machine driver then disable it. Anyway, good, this is what I meant earlier when I said the controls I want to hide are 'useless/confusing at best’. I must walk back that they are ‘dangerous at worst’, but I am glad we can hide them anyway. (Not all of them of course, ISENSE/VSENSE will not be hidden, neither the routing control on systems with single mono speaker.)
WARNING: multiple messages have this Message-ID (diff)
From: "Martin Povišer" <povik@cutebit.org> To: Mark Brown <broonie@kernel.org> Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org, "Sven Peter" <sven@svenpeter.dev>, linux-kernel@vger.kernel.org, "Hector Martin" <marcan@marcan.st>, "Takashi Iwai" <tiwai@suse.com>, "Liam Girdwood" <lgirdwood@gmail.com>, "Rob Herring" <robh+dt@kernel.org>, "Mark Kettenis" <kettenis@openbsd.org>, "Martin Povišer" <povik+lin@cutebit.org>, "Krzysztof Kozlowski" <krzk+dt@kernel.org> Subject: Re: [RFC PATCH 0/5] Apple Macs machine-level ASoC driver Date: Fri, 22 Apr 2022 15:59:25 +0200 [thread overview] Message-ID: <0E735637-EDA8-4A68-8B43-01BCEC41245C@cutebit.org> (raw) In-Reply-To: <YmKoXbh04ZEs3dSZ@sirena.org.uk> > On 22. 4. 2022, at 15:06, Mark Brown <broonie@kernel.org> wrote: > > On Fri, Apr 22, 2022 at 02:53:54PM +0200, Martin Povišer wrote: > >>> Oh, I see - the speaker actually allows configuration of the slots >>> independently. Usually the left/right thing on mono devices only does >>> something for I2S where the bus clocking enforces that there be both >>> left and right channels. Either configuration is fine by me TBH, if you >>> can do that then you could just keep them mapped to the same channel >>> then mark the control as disabled since it should have no effect. > >> Well but is there some established way to mark a control as disabled? > > snd_ctl_activate_id(). Ha! Great. >> Another issue here is that if I disable it I can’t leave the routing >> control in it’s default value, which is ‘I2C Offset’ and makes the speaker >> amp ignore the slot mapping. > > Sure, that's fine - if a control genuinely has no effect it's fine to > hide it from userspace. The issue is where it's just that you don't see > the use, if the control demonstrably does nothing then that's fine. So I assume I can set the control from the machine driver then disable it. Anyway, good, this is what I meant earlier when I said the controls I want to hide are 'useless/confusing at best’. I must walk back that they are ‘dangerous at worst’, but I am glad we can hide them anyway. (Not all of them of course, ISENSE/VSENSE will not be hidden, neither the routing control on systems with single mono speaker.)
next prev parent reply other threads:[~2022-04-22 13:59 UTC|newest] Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-31 0:04 [RFC PATCH 0/5] Apple Macs machine-level ASoC driver Martin Povišer 2022-03-31 0:04 ` Martin Povišer 2022-03-31 0:04 ` [RFC PATCH 1/5] dt-bindings: sound: Add Apple Macs sound system Martin Povišer 2022-03-31 0:04 ` Martin Povišer 2022-03-31 6:43 ` Krzysztof Kozlowski 2022-03-31 6:57 ` Martin Povišer 2022-03-31 8:17 ` Krzysztof Kozlowski 2022-03-31 8:23 ` Martin Povišer 2022-03-31 8:26 ` Krzysztof Kozlowski 2022-03-31 0:04 ` [RFC PATCH 2/5] HACK: ASoC: Add card->filter_controls hook Martin Povišer 2022-03-31 0:04 ` Martin Povišer 2022-03-31 11:34 ` Mark Brown 2022-03-31 11:34 ` Mark Brown 2022-03-31 0:04 ` [RFC PATCH 3/5] HACK: ASoC: Tolerate N-cpus-to-M-codecs links Martin Povišer 2022-03-31 0:04 ` Martin Povišer 2022-04-04 12:28 ` Mark Brown 2022-04-04 12:28 ` Mark Brown 2022-04-22 14:06 ` Martin Povišer 2022-04-22 14:06 ` Martin Povišer 2022-04-25 12:25 ` Mark Brown 2022-04-25 12:25 ` Mark Brown 2022-04-25 12:34 ` Martin Povišer 2022-04-25 12:34 ` Martin Povišer 2022-04-25 12:55 ` Mark Brown 2022-04-25 12:55 ` Mark Brown 2022-04-25 13:11 ` Martin Povišer 2022-04-25 13:11 ` Martin Povišer 2022-04-25 13:46 ` Mark Brown 2022-04-25 13:46 ` Mark Brown 2022-04-25 13:55 ` Martin Povišer 2022-04-25 13:55 ` Martin Povišer 2022-03-31 0:04 ` [RFC PATCH 4/5] ASoC: Introduce snd_soc_of_get_dai_link_cpus Martin Povišer 2022-03-31 0:04 ` Martin Povišer 2022-03-31 0:04 ` [RFC PATCH 5/5] ASoC: Add macaudio machine driver Martin Povišer 2022-03-31 0:04 ` Martin Povišer 2022-03-31 11:59 ` Mark Brown 2022-03-31 11:59 ` Mark Brown 2022-03-31 12:08 ` Martin Povišer 2022-03-31 12:16 ` Martin Povišer 2022-03-31 12:56 ` Mark Brown 2022-03-31 12:56 ` Mark Brown 2022-03-31 12:34 ` [RFC PATCH 0/5] Apple Macs machine-level ASoC driver Mark Brown 2022-03-31 12:34 ` Mark Brown 2022-03-31 13:28 ` Martin Povišer 2022-03-31 14:18 ` Mark Brown 2022-03-31 14:18 ` Mark Brown 2022-03-31 15:04 ` Martin Povišer 2022-03-31 15:36 ` Mark Brown 2022-03-31 15:36 ` Mark Brown 2022-04-22 10:43 ` Martin Povišer 2022-04-22 10:43 ` Martin Povišer 2022-04-22 11:19 ` Mark Brown 2022-04-22 11:19 ` Mark Brown 2022-04-22 11:28 ` Martin Povišer 2022-04-22 11:28 ` Martin Povišer 2022-04-22 11:33 ` Mark Brown 2022-04-22 11:33 ` Mark Brown 2022-04-22 11:44 ` Martin Povišer 2022-04-22 11:44 ` Martin Povišer 2022-04-22 12:22 ` Mark Brown 2022-04-22 12:22 ` Mark Brown 2022-04-22 12:36 ` Martin Povišer 2022-04-22 12:36 ` Martin Povišer 2022-04-22 12:44 ` Mark Brown 2022-04-22 12:44 ` Mark Brown 2022-04-22 12:53 ` Martin Povišer 2022-04-22 12:53 ` Martin Povišer 2022-04-22 13:06 ` Mark Brown 2022-04-22 13:06 ` Mark Brown 2022-04-22 13:59 ` Martin Povišer [this message] 2022-04-22 13:59 ` Martin Povišer 2022-03-31 13:28 ` Hector Martin 2022-03-31 13:28 ` Hector Martin 2022-03-31 14:33 ` Mark Brown 2022-03-31 14:33 ` Mark Brown 2022-04-05 9:31 ` (subset) " Mark Brown 2022-04-05 9:31 ` 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=0E735637-EDA8-4A68-8B43-01BCEC41245C@cutebit.org \ --to=povik@cutebit.org \ --cc=alsa-devel@alsa-project.org \ --cc=broonie@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=kettenis@openbsd.org \ --cc=krzk+dt@kernel.org \ --cc=lgirdwood@gmail.com \ --cc=linux-kernel@vger.kernel.org \ --cc=marcan@marcan.st \ --cc=perex@perex.cz \ --cc=povik+lin@cutebit.org \ --cc=robh+dt@kernel.org \ --cc=sven@svenpeter.dev \ --cc=tiwai@suse.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.