All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Lior Amsalem <alior@marvell.com>, Andrew Lunn <andrew@lunn.ch>,
	Russell King <linux@arm.linux.org.uk>,
	Jason Cooper <jason@lakedaemon.net>,
	Tawfik Bayouk <tawfik@marvell.com>,
	Olof Johansson <olof@lixom.net>,
	linux-pci@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
	Thierry Reding <thierry.reding@avionic-design.de>,
	Grant Likely <grant.likely@secretlab.ca>,
	Maen Suleiman <maen@marvell.com>,
	Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
	Andrew Murray <andrew.murray@arm.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Gregory Clement <gregory.clement@free-electrons.com>,
	Mitch Bradley <wmb@firmworks.com>,
	linux-arm-kernel@lists.infradead.org,
	Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Subject: Re: [RFC PATCHv1 0/5] Use the mvebu PCIe driver on Kirkwood
Date: Wed, 27 Mar 2013 19:18:50 +0100	[thread overview]
Message-ID: <20130327191850.26ab1623@skate> (raw)
In-Reply-To: <20130327191114.2662b3b8@skate>

Arnd,

On Wed, 27 Mar 2013 19:11:14 +0100, Thomas Petazzoni wrote:

> > I assume it works with PIO, but does the SATA card use the I/O
> > space registers, or just memory space?
> 
> Both cards only use memory space. I have a quick and dirty patch for
> the e1000e driver that makes it read/write one particular register from
> the I/O space to test that it works, but I haven't checked this yet on
> Kirkwood. I don't expect much troubles, but who knows.

Just to let you know, I've tested the e1000e with my small changes that
does one I/O access, and it seems to work properly. At least, I read
from the register the value I should be reading (and therefore writing
works, because the I/O space of the e1000e essentially has two
registers: one address register, and one data register, so you must
write one address in the address register before being able to read
something from the data register).

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

WARNING: multiple messages have this Message-ID (diff)
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCHv1 0/5] Use the mvebu PCIe driver on Kirkwood
Date: Wed, 27 Mar 2013 19:18:50 +0100	[thread overview]
Message-ID: <20130327191850.26ab1623@skate> (raw)
In-Reply-To: <20130327191114.2662b3b8@skate>

Arnd,

On Wed, 27 Mar 2013 19:11:14 +0100, Thomas Petazzoni wrote:

> > I assume it works with PIO, but does the SATA card use the I/O
> > space registers, or just memory space?
> 
> Both cards only use memory space. I have a quick and dirty patch for
> the e1000e driver that makes it read/write one particular register from
> the I/O space to test that it works, but I haven't checked this yet on
> Kirkwood. I don't expect much troubles, but who knows.

Just to let you know, I've tested the e1000e with my small changes that
does one I/O access, and it seems to work properly. At least, I read
from the register the value I should be reading (and therefore writing
works, because the I/O space of the e1000e essentially has two
registers: one address register, and one data register, so you must
write one address in the address register before being able to read
something from the data register).

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-03-27 18:18 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27 18:04 [RFC PATCHv1 0/5] Use the mvebu PCIe driver on Kirkwood Thomas Petazzoni
2013-03-27 18:04 ` Thomas Petazzoni
2013-03-27 18:05 ` [RFC PATCHv1 1/5] pci: mvebu: enable driver usage " Thomas Petazzoni
2013-03-27 18:05   ` Thomas Petazzoni
2013-03-27 18:05 ` [RFC PATCHv1 2/5] bus: mvebu: fix mistake in PCIe window target attribute for Kirkwood Thomas Petazzoni
2013-03-27 18:05   ` Thomas Petazzoni
2013-04-03 10:52   ` Thomas Petazzoni
2013-04-03 10:52     ` Thomas Petazzoni
2013-04-03 10:57     ` Jason Cooper
2013-04-03 10:57       ` Jason Cooper
2013-04-03 11:05       ` Thomas Petazzoni
2013-04-03 11:05         ` Thomas Petazzoni
2013-03-27 18:05 ` [RFC PATCHv1 3/5] arm: mach-kirkwood: seperate PCIe window init from other windows Thomas Petazzoni
2013-03-27 18:05   ` Thomas Petazzoni
2013-03-27 18:35   ` Jason Gunthorpe
2013-03-27 18:35     ` Jason Gunthorpe
2013-03-27 20:17     ` Thomas Petazzoni
2013-03-27 20:17       ` Thomas Petazzoni
2013-03-27 18:05 ` [RFC PATCHv1 4/5] arm: kirkwood: add SoC-level Device Tree data for PCIe interfaces Thomas Petazzoni
2013-03-27 18:05   ` Thomas Petazzoni
2013-03-27 18:05 ` [RFC PATCHv1 5/5] arm: kirkwood: convert db-88f6281 to the Device Tree Thomas Petazzoni
2013-03-27 18:05   ` Thomas Petazzoni
2013-03-27 18:07 ` [RFC PATCHv1 0/5] Use the mvebu PCIe driver on Kirkwood Arnd Bergmann
2013-03-27 18:07   ` Arnd Bergmann
2013-03-27 18:11   ` Thomas Petazzoni
2013-03-27 18:11     ` Thomas Petazzoni
2013-03-27 18:18     ` Thomas Petazzoni [this message]
2013-03-27 18:18       ` 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=20130327191850.26ab1623@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=alior@marvell.com \
    --cc=andrew.murray@arm.com \
    --cc=andrew@lunn.ch \
    --cc=arnd@arndb.de \
    --cc=bhelgaas@google.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=grant.likely@secretlab.ca \
    --cc=gregory.clement@free-electrons.com \
    --cc=jason@lakedaemon.net \
    --cc=jgunthorpe@obsidianresearch.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=maen@marvell.com \
    --cc=olof@lixom.net \
    --cc=tawfik@marvell.com \
    --cc=thierry.reding@avionic-design.de \
    --cc=wmb@firmworks.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 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.