From: Hema Kalliguddi <hemahk@ti.com>
To: Sergei Shtylyov <sshtylyov@mvista.com>
Cc: linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
Felipe Balbi <balbi@ti.com>
Subject: RE: [5/7 v2] usb: otg: TWL6030: Introduce the twl6030_phy_suspend function.
Date: Wed, 16 Feb 2011 10:46:30 +0530 [thread overview]
Message-ID: <d9c3feeb60c9efb15f6f365f672d0a35@mail.gmail.com> (raw)
In-Reply-To: <4D5A6FF9.8000709@ru.mvista.com>
Hi,
>-----Original Message-----
>From: Sergei Shtylyov [mailto:sshtylyov@mvista.com]
>Sent: Tuesday, February 15, 2011 5:52 PM
>To: Hema HK
>Cc: linux-usb@vger.kernel.org; linux-omap@vger.kernel.org; Felipe Balbi
>Subject: Re: [5/7 v2] usb: otg: TWL6030: Introduce the
>twl6030_phy_suspend function.
>
>Hello.
>
>On 15-02-2011 12:42, Hema HK wrote:
>
>> From: Kalliguddi, Hema<hemahk@ti.com>
>
>> Introduce the twl6030_phy_suspend function and assign to
>otg.set_suspend
>> function pointer.
>> This function is used by the musb-omap2430 platform driver
>> during suspend/resume.
>
>> Signed-off-by: Hema HK<hemahk@ti.com>
>> Cc: Felipe Balbi<balbi@ti.com>
>
>[...]
>
>> Index: linux-2.6/drivers/usb/otg/twl6030-usb.c
>> ===================================================================
>> --- linux-2.6.orig/drivers/usb/otg/twl6030-usb.c
>> +++ linux-2.6/drivers/usb/otg/twl6030-usb.c
>> @@ -177,6 +177,20 @@ static void twl6030_phy_shutdown(struct
>> pdata->phy_power(twl->dev, 0, 0);
>> }
>>
>> +static int twl6030_phy_suspend(struct otg_transceiver *x,
>int suspend)
>> +{
>> + struct twl6030_usb *twl;
>> + struct device *dev;
>> + struct twl4030_usb_data *pdata;
>> +
>> + twl = xceiv_to_twl(x);
>> + dev = twl->dev;
>> + pdata = dev->platform_data;
>
> Why not do all the above in the intializers?
Can be done that way as well.
Regards,
Hema
>
>> + pdata->phy_suspend(twl->dev, suspend);
>> +
>> + return 0;
>> +}
>> +
>
>WBR, Sergei
>
next prev parent reply other threads:[~2011-02-16 5:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 9:42 [1/7 v2] usb: otg: enable regulator only on cable/device connect Hema HK
[not found] ` <1297762958-26199-1-git-send-email-hemahk-l0cyMroinI0@public.gmane.org>
2011-02-15 9:42 ` [2/7 v2] usb: otg: Remove one unnecessary I2C read request Hema HK
2011-02-15 9:42 ` [4/7 v2] usb: otg: OMAP4430: Add phy_suspend function pointer to Hema HK
2011-02-15 12:18 ` Sergei Shtylyov
[not found] ` <4D5A6F20.5060109-hkdhdckH98+B+jHODAdFcQ@public.gmane.org>
2011-02-16 5:14 ` Hema Kalliguddi
[not found] ` <137f7a77ed983ac5f3d08eaea0b2bb66-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-02-16 11:36 ` Sergei Shtylyov
[not found] ` <4D5BB6BF.7050603-hkdhdckH98+B+jHODAdFcQ@public.gmane.org>
2011-02-16 13:48 ` Hema Kalliguddi
2011-02-15 9:42 ` [5/7 v2] usb: otg: TWL6030: Introduce the twl6030_phy_suspend function Hema HK
[not found] ` <1297762958-26199-5-git-send-email-hemahk-l0cyMroinI0@public.gmane.org>
2011-02-15 12:22 ` Sergei Shtylyov
2011-02-16 5:16 ` Hema Kalliguddi [this message]
2011-02-15 9:42 ` [3/7 v2] usb: otg: OMAP4430: Introducing suspend function for power management Hema HK
2011-02-15 9:42 ` [6/7 v2] usb: otg: TWL6030 Save the last event in otg_transceiver Hema HK
2011-02-15 9:42 ` [7/7 v2] usb: musb: OMAP4430: Fix usb device detection if connected during boot Hema HK
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=d9c3feeb60c9efb15f6f365f672d0a35@mail.gmail.com \
--to=hemahk@ti.com \
--cc=balbi@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sshtylyov@mvista.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox