From: Kim Phillips <kim.phillips@amd.com>
To: Wolfram Sang <wsa@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
<linux-i2c@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Peter Rosin <peda@axentia.se>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Andi Shyti <andi.shyti@kernel.org>
Subject: Re: [PULL REQUEST] i2c-for-6.8-rc1
Date: Wed, 17 Jan 2024 14:35:47 -0600 [thread overview]
Message-ID: <30730c8f-d8f9-4352-ac90-ccec153c32f8@amd.com> (raw)
In-Reply-To: <Zaa2l48Yx1AeCOLs@shikoro>
Hi,
On 1/16/24 11:02 AM, Wolfram Sang wrote:
> The following changes since commit 2cc14f52aeb78ce3f29677c2de1f06c0e91471ab:
>
> Linux 6.7-rc3 (2023-11-26 19:59:33 -0800)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git tags/i2c-for-6.8-rc1
>
> for you to fetch changes up to f4b49e824f0b38e6b5003be97f27c63b96454388:
>
> Revert "i2c: designware: Fix reset call order in dw_i2c_plat_probe()" (2024-01-14 09:02:34 +0100)
>
> ----------------------------------------------------------------
...
> quite some driver updates. Standing out are patches for the wmt-driver
> which is refactored to support more variants. And a big series for the
> designware-driver needed to be reverted because issues have been
> reported late in the cycle and no incremental fix has been found yet.
If you're talking about this original report:
https://lore.kernel.org/lkml/20231229120820.GCZY62tM7z4v2XmOAZ@fat_crate.local/
then my AMD system still fails to boot this pull request's 'i2c-for-6.8-rc1' tag,
and in the same way of the above stack trace.
It looks like a lot of designware commits did indeed get reverted, except the
very first one:
bd466a892612 ( "i2c: designware: Fix PM calls order in dw_i2c_plat_probe()")
If I revert it from 'i2c-for-6.8-rc1', the system boots fine again.
That commit was previously found responsible, here:
https://lore.kernel.org/all/f4b3cc62-8620-4810-97f7-bcc39220b12e@linux.intel.com/
Can that commit also be reverted in this pull request?
Thanks,
Kim
next prev parent reply other threads:[~2024-01-17 20:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 17:02 [PULL REQUEST] i2c-for-6.8-rc1 Wolfram Sang
2024-01-17 20:35 ` Kim Phillips [this message]
2024-01-17 21:00 ` Wolfram Sang
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=30730c8f-d8f9-4352-ac90-ccec153c32f8@amd.com \
--to=kim.phillips@amd.com \
--cc=andi.shyti@kernel.org \
--cc=brgl@bgdev.pl \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=torvalds@linux-foundation.org \
--cc=wsa@kernel.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