From: Stephen Boyd <sboyd@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Jerome Brunet <jbrunet@baylibre.com>,
Arnd Bergmann <arnd@arndb.de>,
Neil Armstrong <neil.armstrong@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-amlogic@lists.infradead.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: amlogic: axg-audio: select RESET_MESON_AUX
Date: Tue, 03 Dec 2024 14:32:56 -0800 [thread overview]
Message-ID: <c982c5061ea6b0d465dd8b7fefc59cc7.sboyd@kernel.org> (raw)
In-Reply-To: <dbb2de3c-cb29-4384-a00b-4fdedeab1a10@sirena.org.uk>
Quoting Mark Brown (2024-12-03 14:22:04)
> On Tue, Dec 03, 2024 at 12:15:48PM -0800, Stephen Boyd wrote:
> > Quoting Jerome Brunet (2024-12-03 03:15:41)
>
> > > I suspect the the generic path is likely to trigger more discussion.
> > > I'd like to be able to finish this migration, instead of leaving half
> > > finished like it is now.
>
> > Is the half finished migration a problem for this cycle? I was intending
> > to send the revert later this week and try again next cycle.
>
> Yes, this patch was triggered by me reporting that multiple boards in my
> test farm have completely broken audio with defconfig.
I thought that commit 5ae1a43486fb ("clk: amlogic: axg-audio: revert
reset implementation") was sufficient to fix the problem. Is that
incorrect?
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Jerome Brunet <jbrunet@baylibre.com>,
Arnd Bergmann <arnd@arndb.de>,
Neil Armstrong <neil.armstrong@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-amlogic@lists.infradead.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: amlogic: axg-audio: select RESET_MESON_AUX
Date: Tue, 03 Dec 2024 14:32:56 -0800 [thread overview]
Message-ID: <c982c5061ea6b0d465dd8b7fefc59cc7.sboyd@kernel.org> (raw)
In-Reply-To: <dbb2de3c-cb29-4384-a00b-4fdedeab1a10@sirena.org.uk>
Quoting Mark Brown (2024-12-03 14:22:04)
> On Tue, Dec 03, 2024 at 12:15:48PM -0800, Stephen Boyd wrote:
> > Quoting Jerome Brunet (2024-12-03 03:15:41)
>
> > > I suspect the the generic path is likely to trigger more discussion.
> > > I'd like to be able to finish this migration, instead of leaving half
> > > finished like it is now.
>
> > Is the half finished migration a problem for this cycle? I was intending
> > to send the revert later this week and try again next cycle.
>
> Yes, this patch was triggered by me reporting that multiple boards in my
> test farm have completely broken audio with defconfig.
I thought that commit 5ae1a43486fb ("clk: amlogic: axg-audio: revert
reset implementation") was sufficient to fix the problem. Is that
incorrect?
next prev parent reply other threads:[~2024-12-03 22:33 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 18:47 [PATCH] clk: amlogic: axg-audio: select RESET_MESON_AUX Jerome Brunet
2024-11-27 18:47 ` Jerome Brunet
2024-11-27 19:00 ` Mark Brown
2024-11-27 19:00 ` Mark Brown
2024-11-27 19:30 ` Arnd Bergmann
2024-11-27 19:30 ` Arnd Bergmann
2024-11-27 20:56 ` Jerome Brunet
2024-11-27 20:56 ` Jerome Brunet
2024-11-27 21:23 ` Arnd Bergmann
2024-11-27 21:23 ` Arnd Bergmann
2024-11-28 13:33 ` Jerome Brunet
2024-11-28 13:33 ` Jerome Brunet
2024-11-28 14:11 ` Arnd Bergmann
2024-11-28 14:11 ` Arnd Bergmann
2024-11-28 14:39 ` Jerome Brunet
2024-11-28 14:39 ` Jerome Brunet
2024-11-28 14:51 ` Arnd Bergmann
2024-11-28 14:51 ` Arnd Bergmann
2024-11-28 15:06 ` Jerome Brunet
2024-11-28 15:06 ` Jerome Brunet
2024-11-28 15:34 ` Arnd Bergmann
2024-11-28 15:34 ` Arnd Bergmann
2024-11-28 15:52 ` Mark Brown
2024-11-28 15:52 ` Mark Brown
2024-11-28 15:57 ` Arnd Bergmann
2024-11-28 15:57 ` Arnd Bergmann
2024-11-28 16:02 ` Jerome Brunet
2024-11-28 16:02 ` Jerome Brunet
2024-11-28 15:53 ` Jerome Brunet
2024-11-28 15:53 ` Jerome Brunet
2024-11-28 17:21 ` Arnd Bergmann
2024-11-28 17:21 ` Arnd Bergmann
2024-12-03 2:53 ` Stephen Boyd
2024-12-03 2:53 ` Stephen Boyd
2024-12-03 11:15 ` Jerome Brunet
2024-12-03 11:15 ` Jerome Brunet
2024-12-03 20:15 ` Stephen Boyd
2024-12-03 20:15 ` Stephen Boyd
2024-12-03 22:22 ` Mark Brown
2024-12-03 22:22 ` Mark Brown
2024-12-03 22:32 ` Stephen Boyd [this message]
2024-12-03 22:32 ` Stephen Boyd
2024-12-03 22:59 ` Mark Brown
2024-12-03 22:59 ` Mark Brown
2024-12-04 17:19 ` Jerome Brunet
2024-12-04 17:19 ` Jerome Brunet
2024-12-04 20:05 ` Stephen Boyd
2024-12-04 20:05 ` Stephen Boyd
2024-12-04 20:10 ` Arnd Bergmann
2024-12-04 20:10 ` Arnd Bergmann
2024-12-03 12:43 ` Arnd Bergmann
2024-12-03 12:43 ` Arnd Bergmann
2024-12-03 20:21 ` Stephen Boyd
2024-12-03 20:21 ` Stephen Boyd
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=c982c5061ea6b0d465dd8b7fefc59cc7.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=mturquette@baylibre.com \
--cc=neil.armstrong@linaro.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 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.