From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: SATA working on 370/XP, Ethernet next...
Date: Fri, 20 Jul 2012 18:12:58 +0200 [thread overview]
Message-ID: <20120720181258.65cbd2fe@skate> (raw)
In-Reply-To: <500981C6.3090109@codethink.co.uk>
Le Fri, 20 Jul 2012 17:05:26 +0100,
Ian Molton <ian.molton@codethink.co.uk> a ?crit :
> > A while ago, we had a discussion with Ben Dooks (from CodeThink) on
> > whether a new driver was needed or not. Ben will correct me if I'm
> > wrong, but he was suggesting that a new driver was not needed, but both
> > Marvell engineers and my comparison of the datasheets between A370/AXP
> > and older Marvell EBU SoCs clearly show that this IP has changed
> > dramatically, and is even not the same IP as before.
> > If needed, I can post the network driver code in a RFC state, but it
> > is clearly not yet ready for inclusion.
>
> I would certainly like to see that if possible, it'd definitley help my
> analysis of the problem.
Ok. I am not sure I wanted to submit this publicly on the netdev
mailing list right now, because the first feeling with a given patch
set is an important one. Would a private submission be possible?
I have been busy the last two days reviewing the code, making many
cleanups on it and collecting comments for the Marvell engineer who
wrote the code initially.
> > I would of course be happy to test SATA patches for the Armada XP.
> > Ian, did you reuse the plat-orion/addr-map.c code to do the window
> > setup? Best regards, Thomas
>
> The code is very similar, and could probably be merged with that. is
> plat-orion meant to now be common to orion, kirkwood, and armada?
Ok, so you duplicated the addr-map.c code?
Initially, I didn't want to use the plat-orion/ code, because I wanted
to replace that with proper drivers (i.e pinctrl driver instead of MPP,
gpio driver in drivers/gpio, proper platform driver for PCI, etc.). But
many drivers (SATA, SDIO, etc.) need the headers file from plat-orion/.
So reusing those drivers without using plat-orion/ is not that simple.
Would you mind sharing the current state of your SATA work, even if not
ready for prime time?
> the window setup code looks horrid to me - we really should look for a
> way to pass this in nicely.
I had started a discussion with Andrew on the mailing list earlier this
week, and we agreed for the moment to re-use the existing code, and see
later what could be done to expose this in the device tree.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-07-20 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 14:41 SATA working on 370/XP, Ethernet next Andrew Lunn
2012-07-20 15:35 ` Ian Molton
2012-07-20 15:52 ` Thomas Petazzoni
2012-07-20 16:05 ` Ian Molton
2012-07-20 16:12 ` Thomas Petazzoni [this message]
2012-07-20 16:25 ` Ian Molton
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=20120720181258.65cbd2fe@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).