From: Alexandru Elisei <alexandru.elisei@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Chen-Yu Tsai <wenst@chromium.org>,
Liam Girdwood <lgirdwood@gmail.com>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: rockchip-i2s: Undo BCLK pinctrl changes
Date: Wed, 13 Jul 2022 17:48:26 +0100 [thread overview]
Message-ID: <Ys73WtpaZLdpsCdL@monolith.localdoman> (raw)
In-Reply-To: <Ys7n+/9v+CygvODo@sirena.org.uk>
On Wed, Jul 13, 2022 at 04:42:51PM +0100, Mark Brown wrote:
> On Wed, Jul 13, 2022 at 03:25:27PM +0100, Alexandru Elisei wrote:
> > On Wed, Jul 13, 2022 at 02:04:51PM +0100, Mark Brown wrote:
> > > The version of the BCLK pinctrl management changes that made it into
> > > v5.19 has caused problems on some systems due to overly strict DT
> > > requirements but attempts to fix it have caused further breakage on
> > > other platforms. Just drop the changes for this release, we already
> > > have a better version queued for -next.
>
> > For what it's worth, I am now able to boot my rockpro64-v2 with this patch.
>
> So Tested-by: then?
Yes, please:
Tested-by: Alexandru Elisei <alexandru.elisei@arm.com>
Thanks,
Alex
WARNING: multiple messages have this Message-ID (diff)
From: Alexandru Elisei <alexandru.elisei@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
Chen-Yu Tsai <wenst@chromium.org>
Subject: Re: [PATCH] ASoC: rockchip-i2s: Undo BCLK pinctrl changes
Date: Wed, 13 Jul 2022 17:48:26 +0100 [thread overview]
Message-ID: <Ys73WtpaZLdpsCdL@monolith.localdoman> (raw)
In-Reply-To: <Ys7n+/9v+CygvODo@sirena.org.uk>
On Wed, Jul 13, 2022 at 04:42:51PM +0100, Mark Brown wrote:
> On Wed, Jul 13, 2022 at 03:25:27PM +0100, Alexandru Elisei wrote:
> > On Wed, Jul 13, 2022 at 02:04:51PM +0100, Mark Brown wrote:
> > > The version of the BCLK pinctrl management changes that made it into
> > > v5.19 has caused problems on some systems due to overly strict DT
> > > requirements but attempts to fix it have caused further breakage on
> > > other platforms. Just drop the changes for this release, we already
> > > have a better version queued for -next.
>
> > For what it's worth, I am now able to boot my rockpro64-v2 with this patch.
>
> So Tested-by: then?
Yes, please:
Tested-by: Alexandru Elisei <alexandru.elisei@arm.com>
Thanks,
Alex
next prev parent reply other threads:[~2022-07-13 17:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 13:04 [PATCH] ASoC: rockchip-i2s: Undo BCLK pinctrl changes Mark Brown
2022-07-13 14:25 ` Alexandru Elisei
2022-07-13 14:25 ` Alexandru Elisei
2022-07-13 15:42 ` Mark Brown
2022-07-13 16:48 ` Alexandru Elisei [this message]
2022-07-13 16:48 ` Alexandru Elisei
2022-07-14 15:46 ` 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=Ys73WtpaZLdpsCdL@monolith.localdoman \
--to=alexandru.elisei@arm.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=wenst@chromium.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.