From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/8] TWL4030 Add usb PHY support
Date: Sun, 06 Sep 2009 08:46:35 -0500 [thread overview]
Message-ID: <4AA3BD3B.2040009@windriver.com> (raw)
In-Reply-To: <20090905000256.GZ30118@game.jcrosoft.org>
Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 15:12 Fri 04 Sep , Tom Rix wrote:
>
<snip>
>>
> please add an empty line
>
I will take care of all the empty lines.
>> + if (ret == 0)
>> + ret = data;
>> + else
>> + printf("TWL4030:USB:Read[0x%x] Error %d\n", address, ret);
>> +
>> + return ret;
>>
> why not this and avoid the copy of data
> if (ret != 0) {
> printf("TWL4030:USB:Read[0x%x] Error %d\n", address, ret);
> return ret;
> }
>
> return data;
> }
>
>
In general I rather have only one exit point from a function.
This makes tracing execution easier.
>> + /* Check if the PHY DPLL is locked */
>> + sts = twl4030_usb_read(TWL4030_USB_PHY_CLK_CTRL_STS);
>> + while (!(sts & PHY_DPLL_CLK) && 0 < timeout) {
>> + udelay(10);
>> + sts = twl4030_usb_read(TWL4030_USB_PHY_CLK_CTRL_STS);
>> + timeout -= 10;
>> + }
>>
> why not set time to 100 * 1000
> and just decrease by 1
>
Yes.
> make some enums by group of function will be better as it simplify the code
>
>> +#define TWL4030_USB_VENDOR_ID_LO 0x00
>> +#define TWL4030_USB_VENDOR_ID_HI 0x01
>>
I see your point, but this is how they are defined in a twl4030 spec.
This way makes it easy to look up #define in the spec.
Just remove the prefix.
>> +#define TWL4030_USB_PRODUCT_ID_LO 0x02
>> +#define TWL4030_USB_PRODUCT_ID_HI 0x03
>>
Tom
>
> Best Regards,
> J.
>
next prev parent reply other threads:[~2009-09-06 13:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 20:12 [U-Boot] [PATCH 1/8] USB Consolidate descriptor definitions Tom Rix
2009-09-04 20:12 ` [U-Boot] [PATCH 2/8] USB add macros for debugging usb device setup Tom Rix
2009-09-04 20:12 ` [U-Boot] [PATCH 3/8] TWL4030 Add usb PHY support Tom Rix
2009-09-04 20:12 ` [U-Boot] [PATCH 4/8] OMAP3 Add usb device support Tom Rix
2009-09-04 20:12 ` [U-Boot] [PATCH 5/8] OMAP3 zoom1 Add usbtty configuration Tom Rix
2009-09-04 20:12 ` [U-Boot] [PATCH 6/8] OMAP3 beagle " Tom Rix
2009-09-04 20:12 ` [U-Boot] [PATCH 7/8] USBTTY make some function declarations easier to use Tom Rix
2009-09-04 20:12 ` [U-Boot] [PATCH 8/8] OMAP3 zoom2 Use usbtty if the debug board is not connected Tom Rix
2009-09-05 0:30 ` Jean-Christophe PLAGNIOL-VILLARD
2009-09-06 13:21 ` Tom
2009-09-05 0:26 ` [U-Boot] [PATCH 6/8] OMAP3 beagle Add usbtty configuration Jean-Christophe PLAGNIOL-VILLARD
2009-09-05 0:26 ` [U-Boot] [PATCH 5/8] OMAP3 zoom1 " Jean-Christophe PLAGNIOL-VILLARD
2009-09-05 0:25 ` [U-Boot] [PATCH 4/8] OMAP3 Add usb device support Jean-Christophe PLAGNIOL-VILLARD
2009-09-06 13:35 ` Tom
2009-09-06 13:48 ` Jean-Christophe PLAGNIOL-VILLARD
2009-09-05 0:02 ` [U-Boot] [PATCH 3/8] TWL4030 Add usb PHY support Jean-Christophe PLAGNIOL-VILLARD
2009-09-06 13:46 ` Tom [this message]
2009-09-06 14:58 ` Jean-Christophe PLAGNIOL-VILLARD
2009-09-05 0:31 ` [U-Boot] [PATCH 2/8] USB add macros for debugging usb device setup Jean-Christophe PLAGNIOL-VILLARD
2009-09-06 13:19 ` Tom
-- strict thread matches above, loose matches on Subject: below --
2009-09-28 16:34 [U-Boot] V2 of OMAP3 USB device Support y at windriver.com
2009-09-28 16:34 ` [U-Boot] [PATCH 1/8] USB Consolidate descriptor definitions y at windriver.com
2009-09-28 16:34 ` [U-Boot] [PATCH 2/8] USB add macros for debugging usb device setup y at windriver.com
2009-09-28 16:34 ` [U-Boot] [PATCH 3/8] TWL4030 Add usb PHY support y at windriver.com
2009-09-28 16:37 [U-Boot] V2 of OMAP3 USB device Support Tom Rix
2009-09-28 16:37 ` [U-Boot] [PATCH 1/8] USB Consolidate descriptor definitions Tom Rix
2009-09-28 16:37 ` [U-Boot] [PATCH 2/8] USB add macros for debugging usb device setup Tom Rix
2009-09-28 16:37 ` [U-Boot] [PATCH 3/8] TWL4030 Add usb PHY support Tom Rix
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=4AA3BD3B.2040009@windriver.com \
--to=tom.rix@windriver.com \
--cc=u-boot@lists.denx.de \
/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