linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kishon@ti.com (Kishon Vijay Abraham I)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH][next] phy: core: make NULL a valid phy reference if !CONFIG_GENERIC_PHY
Date: Thu, 13 Mar 2014 19:13:22 +0530	[thread overview]
Message-ID: <5321B5FA.2030806@ti.com> (raw)
In-Reply-To: <5321B4B4.9010806@ti.com>

Hi Santosh,

On Thursday 13 March 2014 07:07 PM, Santosh Shilimkar wrote:
> On Thursday 13 March 2014 07:11 PM, Strashko, Grygorii wrote:
>> This fixes a regression on Keystone 2 platforms caused by patch
>> 57303488cd37da58263e842de134dc65f7c626d5
>> "usb: dwc3: adapt dwc3 core to use Generic PHY Framework" which adds
>> optional support of generic phy in DWC3 core.
>>
>> On Keystone 2 platforms the USB is not working now because
>> CONFIG_GENERIC_PHY isn't set and, as result, Generic PHY APIs stubs
>> return -ENOSYS always. The log shows:
>>   dwc3 2690000.dwc3: failed to initialize core
>>   dwc3: probe of 2690000.dwc3 failed with error -38
>>
>> Hence, fix it by making NULL a valid phy reference in Generic PHY
>> APIs stubs in the same way as it was done by the patch
>> 04c2facad8fee66c981a51852806d8923336f362 "drivers: phy: Make NULL
>> a valid phy reference".
>>
>> CC: Kishon Vijay Abraham I <kishon@ti.com>
>> CC: Felipe Balbi <balbi@ti.com>
>> CC: Santosh Shilimkar <santosh.shilimkar@ti.com>
>> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
>> ---
> This fixes the regression seen in Linux next and patch seems
> reasonable to me.
> Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
>
> Felipe, Kishon,
> Can you guys pick this fix if you are ok by it. Thanks

I've already given a PULL request to Greg for 3.15. Is it ok to take 
this in -rc cycle?

-Kishon
>
>
>>   include/linux/phy/phy.h |    8 ++++++++
>>   1 file changed, 8 insertions(+)
>>
>> diff --git a/include/linux/phy/phy.h b/include/linux/phy/phy.h
>> index e2f5ca9..5a9b193 100644
>> --- a/include/linux/phy/phy.h
>> +++ b/include/linux/phy/phy.h
>> @@ -204,21 +204,29 @@ static inline void phy_pm_runtime_forbid(struct phy *phy)
>>
>>   static inline int phy_init(struct phy *phy)
>>   {
>> +	if (!phy)
>> +		return 0;
>>   	return -ENOSYS;
>>   }
>>
>>   static inline int phy_exit(struct phy *phy)
>>   {
>> +	if (!phy)
>> +		return 0;
>>   	return -ENOSYS;
>>   }
>>
>>   static inline int phy_power_on(struct phy *phy)
>>   {
>> +	if (!phy)
>> +		return 0;
>>   	return -ENOSYS;
>>   }
>>
>>   static inline int phy_power_off(struct phy *phy)
>>   {
>> +	if (!phy)
>> +		return 0;
>>   	return -ENOSYS;
>>   }
>>
>>
>

  reply	other threads:[~2014-03-13 13:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-13 11:11 [PATCH][next] phy: core: make NULL a valid phy reference if !CONFIG_GENERIC_PHY Grygorii Strashko
2014-03-13 13:37 ` Santosh Shilimkar
2014-03-13 13:43   ` Kishon Vijay Abraham I [this message]
2014-03-13 13:47     ` Santosh Shilimkar
2014-04-16 10:09   ` Kishon Vijay Abraham I
2014-03-13 15:20 ` Felipe Balbi
2014-03-13 21:44   ` Felipe Balbi
2014-04-02 17:53     ` Santosh Shilimkar
2014-04-02 18:16       ` Greg KH
2014-04-02 18:17         ` Santosh Shilimkar
2014-04-02 18:26           ` Greg KH

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=5321B5FA.2030806@ti.com \
    --to=kishon@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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).