All of lore.kernel.org
 help / color / mirror / Atom feed
From: jeffy <jeffy.chen@rock-chips.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	linux-kernel@vger.kernel.org, bhelgaas@google.com,
	Heiko Stuebner <heiko@sntech.de>,
	linux-pci@vger.kernel.org, shawn.lin@rock-chips.com,
	briannorris@chromium.org, dianders@chromium.org,
	linux-rockchip@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
	Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH v5 1/3] PCI: rockchip: Add support for pcie wake irq
Date: Sat, 14 Oct 2017 03:26:16 +0800	[thread overview]
Message-ID: <59E11358.3090409@rock-chips.com> (raw)
In-Reply-To: <20171013191906.GF25517@bhelgaas-glaptop.roam.corp.google.com>

Hi Bjorn,

On 10/14/2017 03:19 AM, Bjorn Helgaas wrote:
> I'm sure they're harmless.  The point is that the cleanup should be
> done near the failure, not in the caller of the caller of the function
> where the failure was detected.  You have:
>
>    rockchip_pcie_probe
>      rockchip_pcie_parse_dt
>        rockchip_pcie_setup_irq
>          err = dev_pm_set_dedicated_wake_irq
>          if (err)
>            dev_err(...)
>
> So you detect the error in rockchip_pcie_setup_irq(), but you clean up
> from it in rockchip_pcie_probe(), which doesn't make sense because
> rockchip_pcie_probe() doesn't do anything related to wakeup interupts.
>
right, but if something wrong happens in rockchip_pcie_probe() later 
than rockchip_pcie_setup_irq(), we may still need to clean it up ;)

i think the error handling is a little like what we do in the remove 
callback
> Bjorn
>
>
>

WARNING: multiple messages have this Message-ID (diff)
From: jeffy.chen@rock-chips.com (jeffy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 1/3] PCI: rockchip: Add support for pcie wake irq
Date: Sat, 14 Oct 2017 03:26:16 +0800	[thread overview]
Message-ID: <59E11358.3090409@rock-chips.com> (raw)
In-Reply-To: <20171013191906.GF25517@bhelgaas-glaptop.roam.corp.google.com>

Hi Bjorn,

On 10/14/2017 03:19 AM, Bjorn Helgaas wrote:
> I'm sure they're harmless.  The point is that the cleanup should be
> done near the failure, not in the caller of the caller of the function
> where the failure was detected.  You have:
>
>    rockchip_pcie_probe
>      rockchip_pcie_parse_dt
>        rockchip_pcie_setup_irq
>          err = dev_pm_set_dedicated_wake_irq
>          if (err)
>            dev_err(...)
>
> So you detect the error in rockchip_pcie_setup_irq(), but you clean up
> from it in rockchip_pcie_probe(), which doesn't make sense because
> rockchip_pcie_probe() doesn't do anything related to wakeup interupts.
>
right, but if something wrong happens in rockchip_pcie_probe() later 
than rockchip_pcie_setup_irq(), we may still need to clean it up ;)

i think the error handling is a little like what we do in the remove 
callback
> Bjorn
>
>
>

  reply	other threads:[~2017-10-13 19:26 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-11 15:10 [PATCH v5 0/3] PCI: rockchip: Move PCIE_WAKE handling into rockchip pcie driver Jeffy Chen
2017-09-11 15:10 ` Jeffy Chen
2017-09-11 15:10 ` Jeffy Chen
2017-09-11 15:10 ` Jeffy Chen
2017-09-11 15:10 ` [PATCH v5 1/3] PCI: rockchip: Add support for pcie wake irq Jeffy Chen
2017-09-11 15:10   ` Jeffy Chen
2017-09-11 15:10   ` Jeffy Chen
2017-09-12  0:39   ` Shawn Lin
2017-09-12  0:39     ` Shawn Lin
2017-09-12  0:39     ` Shawn Lin
2017-10-13  1:56   ` Brian Norris
2017-10-13  1:56     ` Brian Norris
2017-10-13  1:56     ` Brian Norris
2017-10-13  2:32     ` Bjorn Helgaas
2017-10-13  2:32       ` Bjorn Helgaas
2017-10-13  2:32       ` Bjorn Helgaas
2017-10-13  6:31       ` Brian Norris
2017-10-13  6:31         ` Brian Norris
2017-10-13  3:04   ` Bjorn Helgaas
2017-10-13  3:04     ` Bjorn Helgaas
2017-10-13  3:04     ` Bjorn Helgaas
2017-10-13 13:21     ` Rafael J. Wysocki
2017-10-13 13:21       ` Rafael J. Wysocki
2017-10-13 17:58       ` Tony Lindgren
2017-10-13 17:58         ` Tony Lindgren
2017-10-13 18:33       ` jeffy
2017-10-13 18:33         ` jeffy
2017-10-13 19:19         ` Bjorn Helgaas
2017-10-13 19:19           ` Bjorn Helgaas
2017-10-13 19:19           ` Bjorn Helgaas
2017-10-13 19:26           ` jeffy [this message]
2017-10-13 19:26             ` jeffy
2017-10-13 20:44           ` Brian Norris
2017-10-13 20:44             ` Brian Norris
2017-09-11 15:10 ` [PATCH v5 2/3] dt-bindings: PCI: Add definition of " Jeffy Chen
2017-09-11 19:24   ` Rob Herring
2017-09-11 15:10 ` [PATCH v5 3/3] arm64: dts: rockchip: Handle pcie wake in pcie driver for Gru Jeffy Chen
2017-09-11 15:10   ` Jeffy Chen
2017-09-12  0:40   ` Shawn Lin
2017-09-12  0:40     ` Shawn Lin

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=59E11358.3090409@rock-chips.com \
    --to=jeffy.chen@rock-chips.com \
    --cc=bhelgaas@google.com \
    --cc=briannorris@chromium.org \
    --cc=dianders@chromium.org \
    --cc=heiko@sntech.de \
    --cc=helgaas@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=rjw@rjwysocki.net \
    --cc=shawn.lin@rock-chips.com \
    --cc=tony@atomide.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.