linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ray Jui <rjui@broadcom.com>
To: Bjorn Helgaas <bhelgaas@google.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Scott Branden <sbranden@broadcom.com>
Subject: About PCIe PRBS loopback
Date: Tue, 22 Dec 2015 10:21:58 -0800	[thread overview]
Message-ID: <567994C6.8040604@broadcom.com> (raw)

Hi,

We have a PCIe Serdes that is capable of generating some PRBS loopback 
test. Our HW team is using this test to validate the PCIe interfaces on 
our boards. To trigger this test, it requires us to configure the Serdes 
by writing to its registers through an internal MDIO interface.

Does it make any sense to have a standalone kernel driver for this type 
of test? Or test code like this should really belong to a bootloader 
like UEFI or something similar?

Any feedback is appreciated!

Thanks,

Ray

                 reply	other threads:[~2015-12-22 18:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=567994C6.8040604@broadcom.com \
    --to=rjui@broadcom.com \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=sbranden@broadcom.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).