All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: linux-arm-kernel@lists.infradead.org
Cc: "Andrew Lunn" <andrew@lunn.ch>,
	"Gregory Clement" <gregory.clement@bootlin.com>,
	"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Marek Behún" <kabel@kernel.org>, "Pali Rohár" <pali@kernel.org>
Subject: [PATCH 0/2] Fix kernel splats on boot with armada-37xx irqchip driver
Date: Sun, 17 Jul 2022 02:37:43 +0300	[thread overview]
Message-ID: <20220716233745.1704677-1-vladimir.oltean@nxp.com> (raw)

Due to these splats on boot, lockdep disables itself on Armada 37xx and
we fail to see further useful information about real deadlocks.

For those in doubt, the approach to use raw spinlocks for irqchip
drivers has been previously discussed here and doesn't seem too
controversial.
https://lore.kernel.org/lkml/20210825205041.927788-1-vladimir.oltean@nxp.com/

Tested on the Turris MOX board.

Vladimir Oltean (2):
  pinctrl: armada-37xx: make irq_lock a raw spinlock to avoid invalid
    wait context
  pinctrl: armada-37xx: use raw spinlocks for regmap to avoid invalid
    wait context

 drivers/pinctrl/mvebu/pinctrl-armada-37xx.c | 65 +++++++++++++--------
 1 file changed, 40 insertions(+), 25 deletions(-)

-- 
2.34.1


WARNING: multiple messages have this Message-ID (diff)
From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: linux-arm-kernel@lists.infradead.org
Cc: "Andrew Lunn" <andrew@lunn.ch>,
	"Gregory Clement" <gregory.clement@bootlin.com>,
	"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Marek Behún" <kabel@kernel.org>, "Pali Rohár" <pali@kernel.org>
Subject: [PATCH 0/2] Fix kernel splats on boot with armada-37xx irqchip driver
Date: Sun, 17 Jul 2022 02:37:43 +0300	[thread overview]
Message-ID: <20220716233745.1704677-1-vladimir.oltean@nxp.com> (raw)

Due to these splats on boot, lockdep disables itself on Armada 37xx and
we fail to see further useful information about real deadlocks.

For those in doubt, the approach to use raw spinlocks for irqchip
drivers has been previously discussed here and doesn't seem too
controversial.
https://lore.kernel.org/lkml/20210825205041.927788-1-vladimir.oltean@nxp.com/

Tested on the Turris MOX board.

Vladimir Oltean (2):
  pinctrl: armada-37xx: make irq_lock a raw spinlock to avoid invalid
    wait context
  pinctrl: armada-37xx: use raw spinlocks for regmap to avoid invalid
    wait context

 drivers/pinctrl/mvebu/pinctrl-armada-37xx.c | 65 +++++++++++++--------
 1 file changed, 40 insertions(+), 25 deletions(-)

-- 
2.34.1


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2022-07-16 23:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-16 23:37 Vladimir Oltean [this message]
2022-07-16 23:37 ` [PATCH 0/2] Fix kernel splats on boot with armada-37xx irqchip driver Vladimir Oltean
2022-07-16 23:37 ` [PATCH 1/2] pinctrl: armada-37xx: make irq_lock a raw spinlock to avoid invalid wait context Vladimir Oltean
2022-07-16 23:37   ` Vladimir Oltean
2022-07-16 23:37 ` [PATCH 2/2] pinctrl: armada-37xx: use raw spinlocks for regmap " Vladimir Oltean
2022-07-16 23:37   ` Vladimir Oltean
2022-07-18 13:43 ` [PATCH 0/2] Fix kernel splats on boot with armada-37xx irqchip driver Linus Walleij
2022-07-18 13:43   ` Linus Walleij
2022-07-18 14:06   ` Vladimir Oltean
2022-07-18 14:06     ` Vladimir Oltean

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=20220716233745.1704677-1-vladimir.oltean@nxp.com \
    --to=vladimir.oltean@nxp.com \
    --cc=andrew@lunn.ch \
    --cc=gregory.clement@bootlin.com \
    --cc=kabel@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pali@kernel.org \
    --cc=sebastian.hesselbarth@gmail.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 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.