From: Nishanth Menon <nm@ti.com>
To: Sekhar Nori <nsekhar@ti.com>
Cc: Tero Kristo <t-kristo@ti.com>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
Kishon Vijay Abraham I <kishon@ti.com>
Subject: Re: [PATCH] arm64: dts: ti: k3-am65: restrict PCIe to Gen2 speed
Date: Fri, 28 Aug 2020 08:08:24 -0500 [thread overview]
Message-ID: <20200828130824.fupe7keoshwkokgf@akan> (raw)
In-Reply-To: <8c0cc440-4989-413d-e3c8-257d784ec78f@ti.com>
On 17:26-20200828, Sekhar Nori wrote:
> On 28/08/20 5:02 PM, Nishanth Menon wrote:
> > On 08:34-20200828, Sekhar Nori wrote:
> >> On 28/08/20 5:54 AM, Nishanth Menon wrote:
> >>> On 10:13-20200827, Sekhar Nori wrote:
> >>>> Hi Nishanth,
> >>>>
> >>>> On 02/08/20 10:23 PM, Sekhar Nori wrote:
> >>>>> Per errata i2104 documented in AM65x device errata document (TI document
> >>>>> number SPRZ452E, revised June 2019), Gen3 operation is not supported for
> >>>>> both PCIe Root Complex and Endpoint modes of operation.
> >>>>>
> >>>>> See: https://www.ti.com/lit/er/sprz452e/sprz452e.pdf
> >>>>>
> >>>>> Restrict speed to Gen2 to address the errata.
> >>>>>
> >>>>> Signed-off-by: Sekhar Nori <nsekhar@ti.com>
> >>>>
> >>>> Is this in your queue or should I rebase and resend?
> >>>
> >>> Thanks for the reminder. I have put it on my staging branch for now.
> >>> Once rc3 gets tagged with irqchip related changes, I will move this over
> >>> to next.
> >>
> >> Hmm, this is errata fix and fair game for -rc cycle. Can we have this in
> >> v5.9 itself?
> >
> > We could, but does'nt seem urgent enough for 5.9 cycle since the dts node
> > was'nt introduced in this cycle, I think it was introduced around 5.3 or
> > so?
>
> Isn't this too early in -rc cycle to be regressions only?
are'nt we in rc3 already.. But anyways..
>
> I can provide a fixes tag if you want to ensure backporting. I felt odd
> about it because its workaround for hardware issue, nothing wrong in the
> original commit when it was written.
>
> But if you are uncomfortable, fine :)
Thanks. yeah, I'd rather do this for 5.10, too much mayhem in 5.9
cycle already. Need to quiet things a bit here.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-08-28 13:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-02 16:53 [PATCH] arm64: dts: ti: k3-am65: restrict PCIe to Gen2 speed Sekhar Nori
2020-08-27 4:43 ` Sekhar Nori
2020-08-28 0:43 ` Nishanth Menon
[not found] ` <20200828002426.e7surnodpblgln7h@akan>
2020-08-28 3:04 ` Sekhar Nori
2020-08-28 11:32 ` Nishanth Menon
2020-08-28 11:56 ` Sekhar Nori
2020-08-28 13:08 ` Nishanth Menon [this message]
2020-08-31 18:07 ` Nishanth Menon
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=20200828130824.fupe7keoshwkokgf@akan \
--to=nm@ti.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=nsekhar@ti.com \
--cc=t-kristo@ti.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).