From: Bjorn Helgaas <helgaas@kernel.org>
To: "Andrew F. Davis" <afd@ti.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
linux-pci@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH v2 3/7] PCI: dra7xx: Set drvdata at end of probe function
Date: Wed, 12 Oct 2016 17:21:42 -0500 [thread overview]
Message-ID: <20161012222142.GA24545@localhost> (raw)
In-Reply-To: <84f6a4b4-d900-844d-545f-cae1aed299e2@ti.com>
On Wed, Oct 12, 2016 at 02:48:02PM -0500, Andrew F. Davis wrote:
> On 10/12/2016 08:32 AM, Bjorn Helgaas wrote:
> > Set the drvdata pointer at the end of probe function for consistency with
> > other drivers.
>
> I've seen it done the current way many places.
>
> > We don't need the drvdata until after the probe completes,
> > and we don't need it at all if the probe fails.
>
> Are you sure this will always be true? Why not set it as soon as we have
> the ability to, what do we gain by waiting till the end, something like
> one less instruction in the failure case?
I don't think it's likely anybody will need it before .probe()
completes, because the purpose of drvdata is for an external driver
entry point to locate its device data, and none of those entry points
will be called until after .probe() completes successfully.
But I don't care at all if we do it earlier, as long as all the
drivers do it the same way.
Bjorn
next prev parent reply other threads:[~2016-10-12 22:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 13:32 [PATCH v2 0/7] PCI: dra7xx: Cleanups Bjorn Helgaas
2016-10-12 13:32 ` [PATCH v2 1/7] PCI: dra7xx: Add local struct device pointers Bjorn Helgaas
2016-10-12 13:32 ` [PATCH v2 2/7] PCI: dra7xx: Remove redundant struct device pointer from dra7xx_pcie Bjorn Helgaas
2016-10-12 13:32 ` [PATCH v2 3/7] PCI: dra7xx: Set drvdata at end of probe function Bjorn Helgaas
2016-10-12 19:48 ` Andrew F. Davis
2016-10-12 22:21 ` Bjorn Helgaas [this message]
2016-10-13 15:24 ` Andrew F. Davis
2016-10-12 13:33 ` [PATCH v2 4/7] PCI: dra7xx: Use generic DesignWare accessors Bjorn Helgaas
2016-10-12 13:33 ` [PATCH v2 5/7] PCI: dra7xx: Pass device-specific struct to internal functions Bjorn Helgaas
2016-10-12 13:33 ` [PATCH v2 6/7] PCI: dra7xx: Move struct pcie_port setup to probe function Bjorn Helgaas
2016-10-12 19:58 ` Andrew F. Davis
2016-10-12 13:33 ` [PATCH v2 7/7] PCI: dra7xx: Reorder struct dra7xx_pcie Bjorn Helgaas
2016-10-12 16:04 ` [PATCH v2 0/7] PCI: dra7xx: Cleanups Bjorn Helgaas
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=20161012222142.GA24545@localhost \
--to=helgaas@kernel.org \
--cc=afd@ti.com \
--cc=bhelgaas@google.com \
--cc=kishon@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pci@vger.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 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).