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: Fri, 10 Apr 2015 01:27:01 +0200 [thread overview]
Message-ID: <201504100127.01336.marex@denx.de> (raw)
In-Reply-To: <20150409170514.GA4472@Sanchayan-Arch>
On Thursday, April 09, 2015 at 07:05:15 PM, maitysanchayan at gmail.com wrote:
> Hello,
>
> On 15-04-09 18:09:46, Marek Vasut wrote:
> > 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/ .
>
> Not really much VF specific. I was not sure about using the mxs_ prefix
> accessors for VF as well. In the end I found usage in one iMX6 file and
> decided that it makes better sense to actually use the mxs_ existing
> defines. They can be used for Vybrid as well. Except for the non core
> regsiters and a few others no other difference.
>
> I send a v2 version of the patchset based taking your suggestion into
> account. The driver looks cleaner in comparison to the previous :)
> IMHO. Thanks.
>
> https://www.mail-archive.com/u-boot at lists.denx.de/msg168727.html
Roger. If you drop the MXS prefix, feel free to do that in a separate
patch, so this set can go in first :)
next prev parent reply other threads:[~2015-04-09 23:27 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
2015-04-09 17:05 ` maitysanchayan at gmail.com
2015-04-09 23:27 ` Marek Vasut [this message]
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=201504100127.01336.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.