From: maitysanchayan at gmail.com <maitysanchayan@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/6] Add support for Colibri Vybrid Modules
Date: Tue, 14 Apr 2015 15:48:46 +0530 [thread overview]
Message-ID: <20150414101846.GA4504@Sanchayan-Arch.toradex.int> (raw)
In-Reply-To: <BN3PR0301MB08498E574F8C052B4BADD8F781E60@BN3PR0301MB0849.namprd03.prod.outlook.com>
Hello,
On 15-04-14 09:06:27, Peter Chen wrote:
>
>
> > > > > > > >
> > > > > > > > Hi!
> > > > > > > >
> > > > > > > > Stefano, maybe you can pick 1,2,3,4,6 right away for next?
> > > > > > > > This way, we can solve 5/6 separately, since it might need
> > > > > > > > some further dicussion. I don't want that patch to block the
> > > > > > > > rest of the series though.
> > > > > > >
> > > > > > > The sixth patch has some minor dependencies on the fifth patch
> > > > > > > like some #defines and configuration we enable for Colibri. In
> > > > > > > case the fifth patch will require some more discussion and
> > > > > > > time, then I guess I will need to rework the sixth patch and
> > > > > > > then everything related to USB can go in a later patch. The
> > > > > > > rework will be minor. So the v3 will be without USB support
> > > > > >
> > > > > > Well, if you want to rework the 6th patch, that'd be very nice
> > > > > > of you :)
> > > > >
> > > > > Yes sure. Will put the USB support in the end or not, the first
> > > > > patches can go in atleast since there seem to be no complaints on
> > > > > them so far.
> > > > >
> > > > > > > and USB will go in later once this gets applied. Perhaps we
> > > > > > > will send the USB along with some more other featureset
> > > > > > > addition like gpio support for Vybrid which my colleague did
> > > > > > > recently along with some driver model/dt stuff.
> > > > > >
> > > > > > My impression is that the USB is just a matter of figuring out
> > > > > > where the PHY registers go -- whether in
> > > > > > arch/arm/include/imx-common or into include/usb/ . I'd be more
> > > > > > inclined for the later, since the PHY regs looks like chipidea IP specific
> > thing, but I might be wrong.
> > > > >
> > > > > I would say it looks like chipidea specific but I have not looked
> > > > > at IPs other than Freescale controllers to be sure.
> > > >
> > > > I think it's CI-specific indeed, thus include/usb/ . +CC Peter, who
> > > > might chime in whether the PHY is CI-specific or IMX-specific.
> > >
> > > Which PHY? Vybrid? In Linux kernel, it belongs to mxs PHY.
> > > The same controller can integrate different PHYs.
> >
> > Yeah. Is the PHY MXS/IMX/VF specific or can that PHY be found even on other
> > SoCs not manufactured by Freescale ?
> >
>
> This mxs PHY is from SigmaTel, I only see this PHY is used at FSL SoCs, but not sure
> if others use it.
So Chipidea IP with the SigmaTel phy. It might be better to have the
regs-usbphy.h viz. register phy definitions in imx-common then since it
is not clear if SoC's other than Freescale's use the same phy.
Marek, what do you think?
- Sanchayan.
>
> Peter
next prev parent reply other threads:[~2015-04-14 10:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 13:20 [U-Boot] [PATCH v2 0/6] Add support for Colibri Vybrid Modules Sanchayan Maity
2015-04-08 13:20 ` [U-Boot] [PATCH v2 1/6] ARM: vf610: Move DDR3 initialization to imx-common Sanchayan Maity
2015-04-08 13:20 ` [U-Boot] [PATCH v2 2/6] ARM: vf610: Enable external 32KHz oscillator Sanchayan Maity
2015-04-08 13:20 ` [U-Boot] [PATCH v2 3/6] ARM: vf610: Add SoC and CPU type detection Sanchayan Maity
2015-04-08 13:20 ` [U-Boot] [PATCH v2 4/6] ARM: vf610: Enable caches Sanchayan Maity
2015-04-08 13:20 ` [U-Boot] [PATCH v2 5/6] usb: host: Add ehci-vf USB driver for ARM Vybrid SoC's Sanchayan Maity
2015-04-12 23:29 ` Marek Vasut
2015-04-13 5:37 ` maitysanchayan at gmail.com
2015-04-13 5:49 ` Marek Vasut
2015-04-08 13:20 ` [U-Boot] [PATCH v2 6/6] ARM: vf610: Initial integration for Colibri VF50/VF61 Sanchayan Maity
2015-04-11 16:46 ` [U-Boot] [PATCH v2 0/6] Add support for Colibri Vybrid Modules Marek Vasut
2015-04-12 5:33 ` maitysanchayan at gmail.com
2015-04-12 23:28 ` Marek Vasut
2015-04-13 1:36 ` Fabio Estevam
2015-04-13 3:41 ` Marek Vasut
2015-04-13 6:21 ` maitysanchayan at gmail.com
2015-04-13 8:44 ` Marek Vasut
2015-04-13 8:50 ` Peter Chen
2015-04-13 8:52 ` Marek Vasut
2015-04-14 9:06 ` Peter Chen
2015-04-14 10:18 ` maitysanchayan at gmail.com [this message]
2015-04-15 5:41 ` Marek Vasut
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=20150414101846.GA4504@Sanchayan-Arch.toradex.int \
--to=maitysanchayan@gmail.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