From: David Laight <David.Laight@ACULAB.COM>
To: 'Mason' <slash.tmp@free.fr>, Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci <linux-pci@vger.kernel.org>,
linux-usb <linux-usb@vger.kernel.org>,
Rob Herring <robh@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Marc Zyngier <marc.zyngier@arm.com>,
Thibaud Cornic <thibaud_cornic@sigmadesigns.com>,
Phuong Nguyen <phuong_nguyen@sigmadesigns.com>,
Shawn Lin <shawn.lin@rock-chips.com>,
Robin Murphy <robin.murphy@arm.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Kevin Hilman <khilman@kernel.org>
Subject: RE: Neophyte questions about PCIe
Date: Tue, 14 Mar 2017 10:23:53 +0000 [thread overview]
Message-ID: <063D6719AE5E284EB5DD2968C1650D6DCFFB0422@AcuExch.aculab.com> (raw)
In-Reply-To: <826d0a3f-753f-0330-5792-e11beb78d6bf@free.fr>
From: Mason
> Sent: 13 March 2017 21:58
...
> I'd like to push support for this PCIe controller upstream.
>=20
> Is the code I posted on the right track?
> Maybe I can post a RFC patch tomorrow?
I think you need to resolve the problem of config space (and IO) cycles
before the driver can be deemed usable.
David
next prev parent reply other threads:[~2017-03-14 10:23 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 22:45 Neophyte questions about PCIe Mason
2017-03-08 13:39 ` Mason
2017-03-08 13:54 ` David Laight
2017-03-08 14:17 ` Mason
2017-03-08 14:38 ` David Laight
2017-03-09 22:01 ` Jeremy Linton
2017-03-08 15:17 ` Bjorn Helgaas
2017-03-09 23:43 ` Mason
2017-03-10 13:15 ` Robin Murphy
2017-03-10 14:06 ` David Laight
2017-03-10 15:05 ` Mason
2017-03-10 15:14 ` David Laight
2017-03-10 15:33 ` Mason
2017-03-10 15:23 ` Robin Murphy
2017-03-10 15:35 ` David Laight
2017-03-10 16:00 ` Robin Murphy
2017-03-13 10:59 ` Mason
2017-03-13 11:56 ` Robin Murphy
2017-03-10 18:49 ` Bjorn Helgaas
2017-03-10 14:53 ` Mason
2017-03-10 16:45 ` Mason
2017-03-10 17:49 ` Mason
2017-03-11 10:57 ` Mason
2017-03-13 21:40 ` Bjorn Helgaas
2017-03-13 21:57 ` Mason
2017-03-13 22:46 ` Bjorn Helgaas
2017-03-14 10:23 ` David Laight [this message]
2017-03-14 12:05 ` Mason
2017-03-14 12:24 ` David Laight
2017-03-13 14:25 ` Mason
2017-03-14 14:00 ` Mason
2017-03-14 15:54 ` Mason
2017-03-14 21:46 ` Bjorn Helgaas
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=063D6719AE5E284EB5DD2968C1650D6DCFFB0422@AcuExch.aculab.com \
--to=david.laight@aculab.com \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=helgaas@kernel.org \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=phuong_nguyen@sigmadesigns.com \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=shawn.lin@rock-chips.com \
--cc=slash.tmp@free.fr \
--cc=thibaud_cornic@sigmadesigns.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;
as well as URLs for NNTP newsgroup(s).