public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/5] usb: s3c-otg: Split out PHY control
Date: Thu, 6 Nov 2014 21:26:00 +0100	[thread overview]
Message-ID: <201411062126.01101.marex@denx.de> (raw)
In-Reply-To: <20141104193421.GD13607@amd>

On Tuesday, November 04, 2014 at 08:34:21 PM, Pavel Machek wrote:
> On Tue 2014-11-04 06:07:32, Marek Vasut wrote:
> > Split the Samsung specific PHY control into a separate file
> > and compile this into the S3C OTG driver only if used on a
> > Samsung system.
> > 
> > Signed-off-by: Marek Vasut <marex@denx.de>
> > Cc: Chin Liang See <clsee@altera.com>
> > Cc: Dinh Nguyen <dinguyen@opensource.altera.com>
> > Cc: Vince Bridgers <vbridger@altera.com>
> 
> Acked-by: Pavel Machek <pavel@denx.de>
> 
> I know you are just moving the code, but...
> 
> > +void otg_phy_init(struct s3c_udc *dev)
> > +{
> > +	unsigned int usb_phy_ctrl = dev->pdata->usb_phy_ctrl;
> > +	struct s3c_usbotg_phy *phy =
> > +		(struct s3c_usbotg_phy *)dev->pdata->regs_phy;
> > +
> > +	dev->pdata->phy_control(1);
> > +
> > +	/*USB PHY0 Enable */
> 
> Wrong comment style.

I'll fix this one.

> > +	printf("USB PHY0 Enable\n");
> > +
> > +	/* Enable PHY */
> > +	writel(readl(usb_phy_ctrl) | USB_PHY_CTRL_EN0, usb_phy_ctrl);
> 
> We have helpers for setting/clearing bits, right?

Yes we do, Lukasz ... ? :)

Best regards,
Marek Vasut

  reply	other threads:[~2014-11-06 20:26 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04  5:07 [U-Boot] [PATCH 1/5] usb: s3c-otg: Remove useless include Marek Vasut
2014-11-04  5:07 ` [U-Boot] [PATCH 2/5] usb: s3c-otg: Encapsulate PHY control Marek Vasut
2014-11-04 19:30   ` Pavel Machek
2014-11-06  9:43   ` Lukasz Majewski
2014-11-04  5:07 ` [U-Boot] [PATCH 3/5] usb: s3c-otg: Split out " Marek Vasut
2014-11-04 19:34   ` Pavel Machek
2014-11-06 20:26     ` Marek Vasut [this message]
2014-11-07  8:59       ` Lukasz Majewski
2014-11-07  9:12         ` Marek Vasut
2014-11-07 10:08           ` Lukasz Majewski
2014-11-07 10:28             ` Marek Vasut
2014-11-07 14:23               ` Lukasz Majewski
2014-11-07 15:30                 ` Marek Vasut
2014-11-06  9:59   ` Lukasz Majewski
2014-11-06 20:23     ` Marek Vasut
2014-11-06 21:29       ` Lukasz Majewski
2014-11-07  8:05         ` Marek Vasut
2014-11-07 10:40           ` Lukasz Majewski
2014-11-04  5:07 ` [U-Boot] [PATCH 4/5] usb: s3c-otg: Allow custom gusbcfg Marek Vasut
2014-11-04 19:36   ` Pavel Machek
2014-11-06 20:27     ` Marek Vasut
2014-11-07  9:11       ` Lukasz Majewski
2014-11-07  9:25         ` Marek Vasut
2014-11-07 10:22           ` Lukasz Majewski
2014-11-07 14:33           ` Lukasz Majewski
2014-11-07 15:31             ` Marek Vasut
2014-11-04  5:07 ` [U-Boot] [PATCH 5/5] arm: socfpga: Add example UDC config Marek Vasut
2014-11-04 19:51   ` Pavel Machek
2014-11-04 20:09     ` Marek Vasut
2014-11-04 21:01       ` Pavel Machek
2014-11-07 14:40   ` Lukasz Majewski
2014-11-07 14:53     ` Marek Vasut
2014-11-07 15:28       ` Lukasz Majewski
2014-11-07 15:37         ` Marek Vasut
2014-11-07 15:31     ` Marek Vasut
2014-11-04 19:28 ` [U-Boot] [PATCH 1/5] usb: s3c-otg: Remove useless include Pavel Machek
2014-11-06  9:32 ` Lukasz Majewski

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=201411062126.01101.marex@denx.de \
    --to=marex@denx.de \
    --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