From: Chris Packham <chris.packham@alliedtelesis.co.nz>
To: robh+dt@kernel.org, mark.rutland@arm.com, rjui@broadcom.com,
sbranden@broadcom.com, bcm-kernel-feedback-list@broadcom.com,
linus.walleij@linaro.org
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: [PATCH 0/2] ARM: bcm: nsp: gpio improvements (hopefully)
Date: Fri, 25 Oct 2019 17:00:39 +1300 [thread overview]
Message-ID: <20191025040041.6210-1-chris.packham@alliedtelesis.co.nz> (raw)
I'm working on a platform using the BCM 58525 SoC. I noticed that some of
the peripherals were being deferred (not that that's a problem) and debugfs
was complaining "File ':axi@18000000:gpio@20' in directory 'domains' already
present!" which is more of a sign that things were not right.
The debugfs error was because the manually created irq domain was not
cleaned up on failure (or deferral). The deferral was happening because the
pinctrl node had not been probed.
These two patches take care of these problems.
Chris Packham (2):
pinctrl: bcm: nsp: use gpiolib infrastructure for interrupts
ARM: dts: NSP: avoid unnecessary probe deferrals
arch/arm/boot/dts/bcm-nsp.dtsi | 14 ++--
drivers/pinctrl/bcm/pinctrl-nsp-gpio.c | 105 ++++++++++---------------
2 files changed, 49 insertions(+), 70 deletions(-)
--
2.23.0
next reply other threads:[~2019-10-25 4:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 4:00 Chris Packham [this message]
2019-10-25 4:00 ` [PATCH 1/2] pinctrl: bcm: nsp: use gpiolib infrastructure for interrupts Chris Packham
2019-10-25 4:00 ` [PATCH 2/2] ARM: dts: NSP: avoid unnecessary probe deferrals Chris Packham
2019-10-25 17:26 ` Florian Fainelli
2019-10-28 20:21 ` Chris Packham
2019-10-28 21:44 ` Chris Packham
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=20191025040041.6210-1-chris.packham@alliedtelesis.co.nz \
--to=chris.packham@alliedtelesis.co.nz \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.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=mark.rutland@arm.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.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).