From: Stanimir Varbanov <svarbanov@mm-sol.com>
To: "Matwey V. Kornilov" <matwey@sai.msu.ru>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mohit KUMAR <mohit.kumar@st.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: Re: [PATCHv2 1/2] pci: spear: Use platform_driver_probe instead of platform_driver_register
Date: Fri, 13 Feb 2015 04:08:47 +0200 [thread overview]
Message-ID: <54DD5CAF.9040006@mm-sol.com> (raw)
In-Reply-To: <CAJs94EYNs9+Ph3EXZLPEepWJxU_ivXp=Tifq=LkJZ3mwk1fG3g@mail.gmail.com>
Hi,
On 02/12/2015 11:07 AM, Matwey V. Kornilov wrote:
> 2015-02-11 12:19 GMT+03:00 Stanimir Varbanov <svarbanov@mm-sol.com>:
>> please don't top posting.
>>
>> On 02/11/2015 10:38 AM, Matwey V. Kornilov wrote:HI
>>
>>> It sounds reasonable, but does current implementation support deferring?
>>
>>thor
>> yes, it uses deferred probe see devm_phy_get() and devm_clk_get() calls in
>> .probe and how the returned values are checked.
>>
>>> Struct spear13xx_pcie_driver just dissapears from memory after init.
>>
>>
>> IMO this is expected because spear13xx_pcie_driver is annotated as
>> __initdata.
>
> The question was how deferred probe had been expected to work? When
> probe has been deferred at first attempt, then second attempt
> performed after init section, so proble() function must be available,at
> but it is not. Isn't it?
>
That is questionable, maybe it works by chance?.
regards,
Stan
next prev parent reply other threads:[~2015-02-13 2:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 16:31 [PATCHv2 1/2] pci: spear: Use platform_driver_probe instead of platform_driver_register Matwey V. Kornilov
2015-02-10 16:31 ` [PATCHv2 2/2] pci: spear: Drop __initdata from struct platform_driver spear13xx_pcie_driver Matwey V. Kornilov
2015-02-11 3:35 ` [PATCHv2 1/2] pci: spear: Use platform_driver_probe instead of platform_driver_register Viresh Kumar
2015-02-11 7:52 ` Stanimir Varbanov
[not found] ` <CAJs94EYS003e_j0S4rzKFEL=PqCqEmT7yd0qdJdnMrziE1700Q@mail.gmail.com>
2015-02-11 9:19 ` Stanimir Varbanov
2015-02-12 9:07 ` Matwey V. Kornilov
2015-02-13 2:08 ` Stanimir Varbanov [this message]
2015-02-15 13:16 ` Matwey V. Kornilov
2015-02-17 6:17 ` Viresh Kumar
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=54DD5CAF.9040006@mm-sol.com \
--to=svarbanov@mm-sol.com \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matwey@sai.msu.ru \
--cc=mohit.kumar@st.com \
--cc=viresh.kumar@linaro.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.