linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: linux-gpio@vger.kernel.org,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Andy Shevchenko <andy@kernel.org>
Subject: pinctrl-cherryview regression in linux-next on preproduction Braswell
Date: Mon, 3 Jan 2022 11:42:40 +0200	[thread overview]
Message-ID: <70004f1a-fef5-f6e9-6824-47eeb59f8014@linux.intel.com> (raw)

Hi

We have a Braswell based preproduction HW. I noticed linux-next tag 
next-20211224 doesn't boot on it due to following error:

[   34.674271] cherryview-pinctrl INT33FF:00: interrupt on unused 
interrupt line 0
[   34.682476] cherryview-pinctrl INT33FF:00: interrupt on unused 
interrupt line 0
[   34.690681] cherryview-pinctrl INT33FF:00: interrupt on unused 
interrupt line 0
...

Linux v5.16-rc8 is ok. I found the following commit to be reason for the 
regression:

bdfbef2d29dc ("pinctrl: cherryview: Don't use selection 0 to mark an 
interrupt line as unused")

Jarkko

             reply	other threads:[~2022-01-03  9:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03  9:42 Jarkko Nikula [this message]
2022-01-03 10:42 ` pinctrl-cherryview regression in linux-next on preproduction Braswell Hans de Goede
2022-01-03 12:34   ` Jarkko Nikula
2022-01-03 16:06     ` Hans de Goede
2022-01-03 16:40     ` Hans de Goede
2022-01-04  9:43       ` Jarkko Nikula
2022-01-04 10:22         ` Hans de Goede
2022-01-04 10:48           ` Hans de Goede
2022-01-04 14:38             ` Jarkko Nikula
2022-01-04 14:47               ` Hans de Goede
2022-01-05 14:23                 ` Jarkko Nikula
2022-01-10 15:44                   ` Hans de Goede
2022-01-04 15:26           ` Mika Westerberg
2022-01-04 16:37             ` Hans de Goede

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=70004f1a-fef5-f6e9-6824-47eeb59f8014@linux.intel.com \
    --to=jarkko.nikula@linux.intel.com \
    --cc=andy@kernel.org \
    --cc=hdegoede@redhat.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.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: 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;
as well as URLs for NNTP newsgroup(s).