From: Bjorn Helgaas <helgaas@kernel.org>
To: Akshay Bhat <akshay.bhat@timesys.com>
Cc: linux-pci@vger.kernel.org, Tim Harvey <tharvey@gateworks.com>
Subject: Re: [PATCH v2] PCI: imx6: add dt prop for link gen, default to gen1
Date: Wed, 24 Feb 2016 13:52:57 -0600 [thread overview]
Message-ID: <20160224195257.GA31108@localhost> (raw)
In-Reply-To: <loom.20160224T202751-432@post.gmane.org>
[+cc Tim]
On Wed, Feb 24, 2016 at 07:35:55PM +0000, Akshay Bhat wrote:
> Tim Harvey <tharvey <at> gateworks.com> writes:
>
> > >>
> > >> Is there some sort of DT or OF spec that lists "max-link-speed" as a
> > >> generic property? I see Lucas' desire to have this be common across
> > >> DesignWare PCIe cores. Should it be moved up a level even from there,
> > >> i.e., to bindings/pci/pci.txt?
> > >
> > > Bjorn,
> > >
> > > I don't know what the general consensus is here. As your the PCI
> > > maintainer I would leave that up to you. Are there other platforms
> > > that need to link at a lesser capability than the host controller is
> > > capable of? I am only aware of the IMX6 and SPEAr13XX [1]
> > >
> > > I can make that change and re-submit if you feel that is necessary.
> > >
> >
> > Bjorn,
> >
> > Any thoughts here? I would really like to see this get picked up
> > sooner rather than later.
> >
> > Regards,
> >
> > Tim
> >
>
> Bjorn,
>
> It looks like there was no further follow-up on this patch. Could you
> kindly provide feedback to Tim's question? We have multiple i.MX boards
> that could use this patch to resolve PCIe issues.
Tim had mentioned doing a v3 with a documentation update, so I
dropped the v2 patch in anticipation of v3, which never appeared.
Looking at it again, I have another question, so I'll respond to that
thread again.
Bjorn
next prev parent reply other threads:[~2016-02-24 19:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 14:58 [PATCH RFC] PCI: imx6: add dt prop for link gen, default to gen1 Tim Harvey
2015-11-05 15:40 ` Fabio Estevam
2015-11-06 1:15 ` Zhu Richard
2015-11-06 9:36 ` Lucas Stach
2015-11-06 19:59 ` Tim Harvey
2015-11-10 9:49 ` Lucas Stach
2015-11-19 14:12 ` [PATCH v2] " Tim Harvey
2015-11-19 14:19 ` Lucas Stach
2015-11-25 23:14 ` Bjorn Helgaas
2015-12-02 16:35 ` Tim Harvey
2015-12-17 15:09 ` Tim Harvey
2016-02-24 19:35 ` Akshay Bhat
2016-02-24 19:52 ` Bjorn Helgaas [this message]
2016-02-24 20:03 ` Bjorn Helgaas
2016-02-24 20:35 ` Rob Herring
2016-02-29 14:41 ` Tim Harvey
2016-03-01 15:02 ` 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=20160224195257.GA31108@localhost \
--to=helgaas@kernel.org \
--cc=akshay.bhat@timesys.com \
--cc=linux-pci@vger.kernel.org \
--cc=tharvey@gateworks.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.