From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: linux-pci <linux-pci@vger.kernel.org>,
Marek Vasut <marek.vasut+renesas@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Phil Edworthy <phil.edworthy@renesas.com>,
Simon Horman <horms+renesas@verge.net.au>,
Wolfram Sang <wsa@the-dreams.de>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH 2/4] PCI: rcar: Pull bus clock enable/disable from rcar_pcie_get_resources()
Date: Tue, 22 May 2018 17:11:31 +0200 [thread overview]
Message-ID: <CAMuHMdX8_EDhn1+ySeo_eK4eJETGs8ZXS736n92xfv0oNAX4zw@mail.gmail.com> (raw)
In-Reply-To: <20180521131123.2009-2-marek.vasut+renesas@gmail.com>
Hi Marek,
On Mon, May 21, 2018 at 3:11 PM, Marek Vasut <marek.vasut@gmail.com> wrote:
> The rcar_pcie_get_resources() is another misnomer with a side effect.
> The function does not only get resources, but also enables/disables bus
> clock. This is forgotten in the probe() function though and if anything
> in probe() fails after rcar_pcie_get_resources() is called, the bus
> clock are never disabled.
>
> This patch pulls the clock handling out of the rcar_pcie_get_resources()
> and enables clock after all the resources were requested. Moreover, this
> patch also always disables the clock in case of failure.
>
> Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com>
Thanks for your patch!
Reported-by: Geert Uytterhoeven <geert+renesas@glider.be>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2018-05-22 15:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 13:11 [PATCH 1/4] PCI: rcar: Rename rcar_pcie_parse_request_of_pci_ranges() Marek Vasut
2018-05-21 13:11 ` [PATCH 2/4] PCI: rcar: Pull bus clock enable/disable from rcar_pcie_get_resources() Marek Vasut
2018-05-22 9:13 ` Simon Horman
2018-05-22 15:11 ` Geert Uytterhoeven [this message]
2018-05-21 13:11 ` [PATCH 3/4] PCI: rcar: Add missing irq_dispose_mapping() into failpath Marek Vasut
2018-05-22 9:14 ` Simon Horman
2018-05-22 15:18 ` Geert Uytterhoeven
2018-05-22 21:51 ` Marek Vasut
2018-05-21 13:11 ` [PATCH 4/4] PCI: rcar: Teardown MSI setup if rcar_pcie_enable() fails Marek Vasut
2018-05-22 9:16 ` Simon Horman
2018-05-22 18:36 ` Geert Uytterhoeven
2018-05-22 21:53 ` Marek Vasut
2018-05-23 6:18 ` Geert Uytterhoeven
2018-05-23 10:38 ` Marek Vasut
2018-05-22 9:12 ` [PATCH 1/4] PCI: rcar: Rename rcar_pcie_parse_request_of_pci_ranges() Simon Horman
2018-05-22 10:53 ` Geert Uytterhoeven
2018-05-23 16:17 ` Lorenzo Pieralisi
2018-05-23 17:05 ` Marek Vasut
2018-05-23 21:56 ` Bjorn Helgaas
2018-05-24 7:24 ` Marek Vasut
2018-05-24 13:50 ` Lorenzo Pieralisi
2018-05-24 14:36 ` Marek Vasut
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=CAMuHMdX8_EDhn1+ySeo_eK4eJETGs8ZXS736n92xfv0oNAX4zw@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=geert+renesas@glider.be \
--cc=horms+renesas@verge.net.au \
--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=phil.edworthy@renesas.com \
--cc=wsa@the-dreams.de \
/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).