All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Roger Quadros <rogerq@ti.com>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
	tj@kernel.org, sergei.shtylyov@cogentembedded.com,
	b.zolnierkie@samsung.com, hdegoede@redhat.com,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, Balaji T K <balajitk@ti.com>
Subject: Re: [PATCH v3 2/3] ata: ahci_platform: Manage SATA PHY
Date: Thu, 9 Jan 2014 11:05:20 +0100	[thread overview]
Message-ID: <201401091105.20727.arnd@arndb.de> (raw)
In-Reply-To: <52CE40FA.5070605@ti.com>

On Thursday 09 January 2014, Roger Quadros wrote:
> >> if (!IS_ERR(hpriv->phy)) {
> >>         rc = phy_init(hpriv->phy);
> >>         if (rc)
> >>                 goto disable_unprepare_clk;
> >>
> >>         rc = phy_power_on(hpriv->phy);
> >>         if (rc) {
> >>                 phy_exit(hpriv->phy);
> >>                 goto disable_unprepare_clk;
> >>         }
> >> }
> > 
> > As I said, I'd prefer to set hpriv->phy to NULL in case of -ENODEV,
> > but functionally it seems right (with the fixup from your other mail).
> > 
> 
> Why do you prefer setting hpriv->phy to NULL instead of using IS_ERR() check
> before hpriv->phy is used?
> The latter seems to be the norm at least among clock framework users.

Two reasons:

1. It feels more natural to read "if (clk)" in driver code as a check for
   "a clock exists" than "if (!IS_ERR(clk))".
2. It clarifies that this code path is only there to check for the
   clk-not-present case, not for other errors.

Obviously the first check after clk_get needs to be IS_ERR() because that
is the documented interface, but then you should decide on the action
based on the specific error.

	Arnd

  reply	other threads:[~2014-01-09 10:05 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08  9:47 [PATCH v3 0/3] ata: ahci_platform: Add PHY support and OMAP support Roger Quadros
2014-01-08  9:47 ` Roger Quadros
2014-01-08  9:47 ` [PATCH v3 1/3] ata: ahci_platform: Update DT compatible list Roger Quadros
2014-01-08  9:47   ` Roger Quadros
2014-01-08  9:47 ` [PATCH v3 2/3] ata: ahci_platform: Manage SATA PHY Roger Quadros
2014-01-08  9:47   ` Roger Quadros
     [not found]   ` <1389174428-31414-3-git-send-email-rogerq-l0cyMroinI0@public.gmane.org>
2014-01-08  9:59     ` Kishon Vijay Abraham I
2014-01-08  9:59       ` Kishon Vijay Abraham I
     [not found]       ` <52CD2176.6050102-l0cyMroinI0@public.gmane.org>
2014-01-08 10:05         ` Arnd Bergmann
2014-01-08 10:05           ` Arnd Bergmann
2014-01-08 11:28           ` Roger Quadros
2014-01-08 11:28             ` Roger Quadros
2014-01-08 11:33             ` Roger Quadros
2014-01-08 11:33               ` Roger Quadros
2014-01-08 11:46             ` Arnd Bergmann
2014-01-09  6:26               ` Roger Quadros
2014-01-09  6:26                 ` Roger Quadros
2014-01-09 10:05                 ` Arnd Bergmann [this message]
2014-01-08 13:14             ` Hans de Goede
     [not found]               ` <52CD4F2A.9080301-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-01-08 15:55                 ` Hans de Goede
2014-01-08 15:55                   ` Hans de Goede
2014-01-08  9:47 ` [PATCH v3 3/3] ata: ahci_platform: runtime resume the device before use Roger Quadros
2014-01-08  9:47   ` Roger Quadros

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=201401091105.20727.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=b.zolnierkie@samsung.com \
    --cc=balajitk@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hdegoede@redhat.com \
    --cc=kishon@ti.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rogerq@ti.com \
    --cc=sergei.shtylyov@cogentembedded.com \
    --cc=tj@kernel.org \
    /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.