linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Cvek <petrcvekcz@gmail.com>
To: ryder.lee@mediatek.com, blogic@openwrt.org, sergio.paracuellos@gmail.com
Cc: linux-mediatek@lists.infradead.org, linux-mips@linux-mips.org,
	linux-pci@vger.kernel.org
Subject: mt7621/mt7628 PCIe linux driver
Date: Sat, 22 Sep 2018 23:06:50 +0200	[thread overview]
Message-ID: <8fd595af-53fa-c100-c369-8c7a30eba8e3@gmail.com> (raw)

Hello,

I'm trying to play with mt7628 PCIe (and it's old driver mt7620), but
the system keeps freezing. It is probably because of bus master access
of my PCIe cards but I don't see any memory access controls for PCIe <->
RAM in the datasheet. The same problem is with MSI. It seems the root
complex supports MSI (it has an MSI capability field), but there isn't
any mention in the MT7628 datasheet too. As it seems the MT7628 PCIe is
based on MT7621 PCIe, I went for an MT7621 datasheet, but sadly in the
datasheet the PCIe section is missing completely.

Does anybody have a working MT7621/28 bus master setup or a more
completed datasheet? I would like to get some information for fixing the
mt7620 PCIe driver. It is possible the MSI/bus master is controlled by
the undocumented bridge registers (in the pci-mt7621 they controls the
manual oscillator settings, I've found a link quality register at
0x101490c4) or in a PCI config space of the root complex (around 0x700
offset). If you have a working SoC with MSI/bus mastering (= mem access
from card), can you send me the dump of there spaces?

Thanks

best regards,
Petr

             reply	other threads:[~2018-09-22 21:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-22 21:06 Petr Cvek [this message]
2018-09-23  6:20 ` mt7621/mt7628 PCIe linux driver Sergio Paracuellos
2018-10-07 13:25   ` Petr Cvek
2018-10-08  4:20     ` Sergio Paracuellos

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=8fd595af-53fa-c100-c369-8c7a30eba8e3@gmail.com \
    --to=petrcvekcz@gmail.com \
    --cc=blogic@openwrt.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=ryder.lee@mediatek.com \
    --cc=sergio.paracuellos@gmail.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).