From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RESEND PATCH 5/6] usb: host: Add ehci-vf USB driver for ARM Vybrid SoC's
Date: Thu, 9 Apr 2015 18:09:46 +0200 [thread overview]
Message-ID: <201504091809.47040.marex@denx.de> (raw)
In-Reply-To: <20150407070345.GA4656@Sanchayan-Arch.toradex.int>
On Tuesday, April 07, 2015 at 09:03:45 AM, maitysanchayan at gmail.com wrote:
> Hello,
>
> On 15-04-01 21:15:21, Marek Vasut wrote:
> > On Wednesday, April 01, 2015 at 11:54:22 AM, Sanchayan Maity wrote:
> >
> > The commit message is missing, please fix in v2.
> >
> > > Signed-off-by: Sanchayan Maity <maitysanchayan@gmail.com>
> >
> > [...]
> >
> > > +#define USB_NC_REG_OFFSET 0x00000800
> > > +#define USBCx_CTRL_OFFSET 0x00000000
> > > +#define USBCx_PHY_CTRL_OFFSET 0x00000018
> >
> > Please define the register offsets using the regular struct {} method,
> > see for example struct mxs_usbphy_regs and it's usage in ehci-mxs.c .
>
> I had a query here, just to be sure and avoid rework. The vybrid defines
> would be similar to mxs. I assume I can add them to the regs-common.h
> file along with a note that the VF610 also has the same _set, _clr,
> _tog register? Or perhaps it would be more appropriate to have the file
> have generic names which mxs, vf and imx can all leverage? Though for
> now this would require reworking all the three drivers.
>
> The USB phy definitions part is ok, as they would go in the arch
> specific folder.
If these are really IMX/MXS/VF specific, then the defines should go into
arch/arm/include/asm/imx-common/ . Otherwise, you can make chipidea specific
file in include/usb/ .
> > > +#define USBPHY_CTRL
0x00000030
> > > +#define USBPHY_CTRL_SET 0x00000034
> > > +#define USBPHY_CTRL_CLR 0x00000038
> > > +#define USBPHY_CTRL_TOG 0x0000003c
> > > +
> > > +#define USBPHY_PWD
0x00000000
> > > +#define USBPHY_TX
0x00000010
> > > +#define USBPHY_RX
0x00000020
> > > +#define USBPHY_DEBUG 0x00000050
> > > +#define USBPHY_CTRL_SFTRST 0x80000000
> > > +#define USBPHY_CTRL_CLKGATE 0x40000000
> > > +#define USBPHY_CTRL_ENUTMILEVEL3 0x00008000
> > > +#define USBPHY_CTRL_ENUTMILEVEL2 0x00004000
> > > +#define USBPHY_CTRL_OTG_ID 0x08000000
> > > +
> > > +#define ANADIG_PLL_CTRL_BYPASS 0x00010000
> > > +#define ANADIG_PLL_CTRL_ENABLE 0x00002000
> > > +#define ANADIG_PLL_CTRL_POWER 0x00001000
> > > +#define ANADIG_PLL_CTRL_EN_USB_CLKS 0x00000040
> > > +
> > > +#define UCTRL_OVER_CUR_POL (1 << 8) /* OTG Polarity of Overcurrent
*/
> > > +#define UCTRL_OVER_CUR_DIS (1 << 7) /* Disable OTG Overcurrent
> > > Detection */ +
> > > +/* USBCMD */
> > > +#define UCMD_RUN_STOP (1 << 0) /* controller run/stop */
> > > +#define UCMD_RESET (1 << 1) /* controller reset */
> >
> > This looks very much like the USB PHY used on MX28 , can you double-check
> > this please ?
>
> MX28 IP also seems similar to the Vybrid USB IP except for a few
> registers and the non core registers. Perhaps to be expected as they all
> have a common chipidea IP core, though having a different version
> thereof.
Yep, I agree :)
Thanks!
next prev parent reply other threads:[~2015-04-09 16:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 9:54 [U-Boot] [RESEND PATCH 0/6] Add support for Colibri Vybrid Modules Sanchayan Maity
2015-04-01 9:54 ` [U-Boot] [RESEND PATCH 1/6] ARM: vf610: Move DDR3 initialization to imx-common Sanchayan Maity
2015-04-01 9:54 ` [U-Boot] [RESEND PATCH 2/6] ARM: vf610: Enable external 32KHz oscillator Sanchayan Maity
2015-04-01 9:54 ` [U-Boot] [RESEND PATCH 3/6] ARM: vf610: Add SoC and CPU type detection Sanchayan Maity
2015-04-01 9:54 ` [U-Boot] [RESEND PATCH 4/6] ARM: vf610: Enable caches Sanchayan Maity
2015-04-01 9:54 ` [U-Boot] [RESEND PATCH 5/6] usb: host: Add ehci-vf USB driver for ARM Vybrid SoC's Sanchayan Maity
2015-04-01 19:15 ` Marek Vasut
2015-04-02 10:55 ` maitysanchayan at gmail.com
2015-04-02 16:47 ` Marek Vasut
2015-04-07 7:03 ` maitysanchayan at gmail.com
2015-04-09 16:09 ` Marek Vasut [this message]
2015-04-09 17:05 ` maitysanchayan at gmail.com
2015-04-09 23:27 ` Marek Vasut
2015-04-09 16:51 ` Fabio Estevam
2015-04-09 23:26 ` Marek Vasut
2015-04-01 9:54 ` [U-Boot] [RESEND PATCH 6/6] ARM: vf610: Initial integration for Colibri VF50/VF61 Sanchayan Maity
2015-04-01 10:44 ` Stefan Agner
2015-04-01 11:27 ` [U-Boot] [RESEND PATCH 0/6] Add support for Colibri Vybrid Modules Tom Rini
2015-04-02 10:58 ` maitysanchayan at gmail.com
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=201504091809.47040.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