From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: marek.vasut@gmail.com, linux-pci@vger.kernel.org
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Wolfram Sang <wsa@the-dreams.de>,
linux-renesas-soc@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Randy Dunlap <rdunlap@infradead.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Stephen Boyd <sboyd@kernel.org>,
Marek Vasut <marek.vasut+renesas@gmail.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH v4] PCI: rcar: Check if device is runtime suspended instead of __clk_is_enabled()
Date: Wed, 1 Dec 2021 16:24:26 +0000 [thread overview]
Message-ID: <163837585219.20378.14215787015819697563.b4-ty@arm.com> (raw)
In-Reply-To: <20211115204641.12941-1-marek.vasut@gmail.com>
On Mon, 15 Nov 2021 21:46:41 +0100, marek.vasut@gmail.com wrote:
> From: Marek Vasut <marek.vasut+renesas@gmail.com>
>
> Replace __clk_is_enabled() with pm_runtime_suspended(),
> as __clk_is_enabled() was checking the wrong bus clock
> and caused the following build error too:
> arm-linux-gnueabi-ld: drivers/pci/controller/pcie-rcar-host.o: in function `rcar_pcie_aarch32_abort_handler':
> pcie-rcar-host.c:(.text+0xdd0): undefined reference to `__clk_is_enabled'
>
> [...]
Applied to pci/rcar, thanks!
[1/1] PCI: rcar: Check if device is runtime suspended instead of __clk_is_enabled()
https://git.kernel.org/lpieralisi/pci/c/d2a14b5498
Thanks,
Lorenzo
prev parent reply other threads:[~2021-12-01 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 20:46 [PATCH v4] PCI: rcar: Check if device is runtime suspended instead of __clk_is_enabled() marek.vasut
2021-11-15 21:59 ` Krzysztof Wilczyński
2021-12-01 16:24 ` Lorenzo Pieralisi [this message]
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=163837585219.20378.14215787015819697563.b4-ty@arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=geert+renesas@glider.be \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut+renesas@gmail.com \
--cc=marek.vasut@gmail.com \
--cc=rdunlap@infradead.org \
--cc=sboyd@kernel.org \
--cc=wsa@the-dreams.de \
--cc=yoshihiro.shimoda.uh@renesas.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.