From: "Martin Povišer" <povik+lin@cutebit.org>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>, Stephen Kitt <steve@sk2.org>,
raphael-xu@ti.com, alsa-devel@alsa-project.org, asyrus@ti.com,
Charles Keepax <ckeepax@opensource.cirrus.com>,
navada@ti.com, linux-kernel@vger.kernel.org,
shenghao-ding@ti.com
Subject: Re: [PATCH 0/2] Untested TAS2562 power setting fixes
Date: Mon, 5 Sep 2022 17:45:09 +0200 [thread overview]
Message-ID: <C600ACEB-C64F-4501-94E4-17B4FD0A8918@cutebit.org> (raw)
In-Reply-To: <166239232739.736206.17258746656389143736.b4-ty@kernel.org>
> On 5. 9. 2022, at 17:38, Mark Brown <broonie@kernel.org> wrote:
>
> On Thu, 25 Aug 2022 16:22:24 +0200, Martin Povišer wrote:
>> The tas2562 driver does the same thing with the setting of PWR_CTRL
>> field as the tas2764/tas2770 drivers were doing.
>> Link: https://lore.kernel.org/alsa-devel/20220808141246.5749-1-povik+lin@cutebit.org/T/#t
>> Link: https://lore.kernel.org/alsa-devel/20220825140241.53963-1-povik+lin@cutebit.org/T/#t
>>
>> These are blindly written patches without testing since I don't have
>> the hardware. (I even tried TI's formal sample request program but
>> was refused there. CCing @ti.com addresses I found on other series
>> recently submitted.)
>>
>> [...]
>
> Applied to
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
>
> Thanks!
Texas Instruments is shipping me samples of the affected
codecs, so I should be able to test the changes on hardware soon.
Should I find regressions, I will report back.
Martin
next prev parent reply other threads:[~2022-09-05 15:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 14:22 Martin Povišer
2022-08-25 14:22 ` [PATCH 1/2] ASoC: tas2562: Drop conflicting set_bias_level power setting Martin Povišer
2022-08-25 14:22 ` [PATCH 2/2] ASoC: tas2562: Fix mute/unmute Martin Povišer
[not found] ` <166239232739.736206.17258746656389143736.b4-ty@kernel.org>
2022-09-05 15:45 ` Martin Povišer [this message]
2022-09-05 16:42 ` [PATCH 0/2] Untested TAS2562 power setting fixes 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=C600ACEB-C64F-4501-94E4-17B4FD0A8918@cutebit.org \
--to=povik+lin@cutebit.org \
--cc=alsa-devel@alsa-project.org \
--cc=asyrus@ti.com \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=navada@ti.com \
--cc=raphael-xu@ti.com \
--cc=shenghao-ding@ti.com \
--cc=steve@sk2.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
all inboxes | Powered by JetHome®