mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Jason Cooper <jason@lakedaemon.net>
Cc: barebox@lists.infradead.org,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH RFC 0/4] MVEBU SoC full USB support
Date: Thu, 26 Jun 2014 14:08:11 +0200	[thread overview]
Message-ID: <53AC0D2B.3090803@gmail.com> (raw)
In-Reply-To: <53AB229B.1010104@gmail.com>

On 06/25/2014 09:27 PM, Sebastian Hesselbarth wrote:
> On 06/25/2014 09:18 PM, Jason Cooper wrote:
>> On Wed, Jun 25, 2014 at 04:08:44PM +0200, Sebastian Hesselbarth wrote:
>>> This *RFC* adds a driver stub for ChipIdea USB dual role controllers
>>> found on Marvell MVEBU SoCs. Although, I consider this driver quite
>>> finished, the corresponding DT binding is not. Also, we currently
>>> have no corresponding driver in Linux for both MVEBU CI stub and
>>> USB PHY.
>>>
>>> The reason I send it here and now, is to get some input from the
>>> (Linux) MVEBU guys on the binding and functional tests on Armada XP.
>>
>> My first thought is if this chipidea IP is used beyond the mvebu
>> ecosystem.  Shouldn't we name it and it's compatible strings with
>> 'chipidea' instead of 'marvell'?
>
> While the IP core is CI, you remember the mbus upstream registers?
> That registers are very special to MVEBU SoCs and make the IP itself
> "marvell".

While working with Dove's SDHCI, I thought about the upstream registers
again. Dove's SDHCI shares those registers with Camera IP which makes
it difficult to find a good DT representation again.

Maybe we should think about moving upstream register setup to mbus
driver instead? That would also allow us to get rid of mvebu specific
boiler plates from those standard (fooHCI) IP drivers.

Sebastian


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2014-06-26 12:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-25 14:08 Sebastian Hesselbarth
2014-06-25 14:08 ` [PATCH RFC 1/4] usb: add Marvell MVEBU " Sebastian Hesselbarth
2014-06-30  6:30   ` Sascha Hauer
2014-06-30  7:46     ` Sebastian Hesselbarth
2014-06-25 14:08 ` [PATCH RFC 2/4] ARM: dts: add new USB nodes to Kirkwood Guruplug Sebastian Hesselbarth
2014-06-25 14:08 ` [PATCH RFC 3/4] ARM: dts: add new USB nodes to Dove CuBox Sebastian Hesselbarth
2014-06-25 14:08 ` [PATCH RFC 4/4] ARM: dts: add new USB nodes to Armada 370 Mirabox Sebastian Hesselbarth
2014-06-25 19:18 ` [PATCH RFC 0/4] MVEBU SoC full USB support Jason Cooper
2014-06-25 19:27   ` Sebastian Hesselbarth
2014-06-26 12:08     ` Sebastian Hesselbarth [this message]
2014-06-25 19:40 ` Thomas Petazzoni

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=53AC0D2B.3090803@gmail.com \
    --to=sebastian.hesselbarth@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=barebox@lists.infradead.org \
    --cc=jason@lakedaemon.net \
    --cc=thomas.petazzoni@free-electrons.com \
    /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