From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [V7 PATCH 01/16] usb: phy: mv_usb2: add PHY driver for marvell usb2 controller
Date: Mon, 18 Feb 2013 09:47:00 +0200 [thread overview]
Message-ID: <20130218074700.GD29848@arwen.pp.htv.fi> (raw)
In-Reply-To: <CADApbei9u2LLSgA7E0vwRZ-iKAh7usqETzrsMSqdT5+6WZ3y+w@mail.gmail.com>
Hi,
On Mon, Feb 18, 2013 at 02:58:29PM +0800, Chao Xie wrote:
> >> +static unsigned int u2o_get(void __iomem *base, unsigned int offset)
> >> +{
> >> + return readl(base + offset);
> >> +}
> >> +
> >> +static void u2o_set(void __iomem *base, unsigned int offset,
> >> + unsigned int value)
> >> +{
> >> + u32 reg;
> >> +
> >> + reg = readl(base + offset);
> >> + reg |= value;
> >> + writel(reg, base + offset);
> >> + readl(base + offset);
> >
> >
> > spurious readl.
> >
> Writing to the PHY setting registers has to make sure that every
> writing has been issued already.
> The design engineer suggest us to add reading after the writing. It
> can make sure the writing has
> taken effect.
add a comment explaining that, then.
> >> + _mv_usb2_phy_shutdown(mv_phy);
> >> + for (i = 0; i < mv_phy->clks_num; i++)
> >> + clk_disable_unprepare(mv_phy->clks[i]);
> >> + }
> >> + usb_add_phy_dev(&mv_phy->phy);
> >> +
> >> + platform_set_drvdata(pdev, mv_phy);
> >> +
> >> + dev_info(&pdev->dev, "mv usb2 phy initialized\n");
> >
> >
> > dev_info makes the boot log noisy.
> >
> It is the only print in boot log for usb phy.
> I can change it to be dev_dbg.
you can manage completely without it.
--
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130218/bc2d6fad/attachment.sig>
next prev parent reply other threads:[~2013-02-18 7:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 6:10 [V7 PATCH 00/16] mv-usb phy enhancement patches Chao Xie
2013-02-18 6:10 ` [V7 PATCH 01/16] usb: phy: mv_usb2: add PHY driver for marvell usb2 controller Chao Xie
2013-02-18 6:43 ` kishon
2013-02-18 6:58 ` Chao Xie
2013-02-18 7:47 ` Felipe Balbi [this message]
2013-02-18 6:10 ` [V7 PATCH 02/16] usb: gadget: mv_udc: use PHY driver for udc Chao Xie
2013-02-18 8:20 ` kishon
2013-02-18 6:10 ` [V7 PATCH 03/16] usb: ehci: ehci-mv: use PHY driver for ehci Chao Xie
2013-02-18 6:10 ` [V7 PATCH 04/16] usb: otg: mv_otg: use PHY driver for otg Chao Xie
2013-02-18 6:10 ` [V7 PATCH 05/16] arm: mmp2: change the defintion of usb devices Chao Xie
2013-02-18 6:10 ` [V7 PATCH 06/16] arm: pxa910: " Chao Xie
2013-02-18 6:10 ` [V7 PATCH 07/16] arm: brownstone: add usb support for the board Chao Xie
2013-02-18 6:10 ` [V7 PATCH 08/16] arm: ttc_dkb: add usb support Chao Xie
2013-02-18 6:10 ` [V7 PATCH 09/16] arm: mmp: remove the usb phy setting Chao Xie
2013-02-18 6:10 ` [V7 PATCH 10/16] arm: mmp: remove usb devices from pxa168 Chao Xie
2013-02-18 6:10 ` [V7 PATCH 11/16] usb: phy: mv_usb2_phy: add externel chip support Chao Xie
2013-02-18 6:10 ` [V7 PATCH 12/16] usb: gadget: mv_udc: add extern " Chao Xie
2013-02-18 6:10 ` [V7 PATCH 13/16] usb: ehci: ehci-mv: " Chao Xie
2013-02-18 6:10 ` [V7 PATCH 14/16] usb: otg: mv_otg: " Chao Xie
2013-02-18 6:10 ` [V7 PATCH 15/16] arm: mmp: add extern chip support for brownstone Chao Xie
2013-02-18 6:10 ` [V7 PATCH 16/16] arm: mmp: add extern chip support for ttc_dkb Chao Xie
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=20130218074700.GD29848@arwen.pp.htv.fi \
--to=balbi@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