All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/6] Add support for Colibri Vybrid Modules
Date: Mon, 13 Apr 2015 01:28:07 +0200	[thread overview]
Message-ID: <201504130128.07449.marex@denx.de> (raw)
In-Reply-To: <20150412053341.GA1862@Sanchayan-Arch>

On Sunday, April 12, 2015 at 07:33:41 AM, maitysanchayan at gmail.com wrote:
> Hi,
> 
> On 15-04-11 18:46:15, Marek Vasut wrote:
> > On Wednesday, April 08, 2015 at 03:20:04 PM, Sanchayan Maity wrote:
> > > Hello,
> > > 
> > > This is the second version of the patchset which adds support for the
> > > Toradex Colibri Vybrid VF50 and VF61 modules. Boot up has been tested
> > > using the serial loader over UART.
> > 
> > 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 :)

> 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.

> By the way, where the fifth patch is concerned, is it related to the
> discussion Fabio pointed out in the discussion on first version of the
> patch? uboot trying to get rid of the 'no register access via offset'
> rule? Anything required I can rework accordingly.

I was concerned about the placement of the PHY reg definition. I didn't
hear from Fabio on the result of this decision and I don't really mind
that either way.

Best regards,
Marek Vasut

  reply	other threads:[~2015-04-12 23:28 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 [this message]
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
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=201504130128.07449.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.