From: Bjorn Helgaas <helgaas@kernel.org>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: linux-pci@vger.kernel.org, gregkh@linuxfoundation.org,
bhelgaas@google.com, kw@linux.com, robh@kernel.org,
lpieralisi@kernel.org
Subject: Re: [PATCH] PCI: mt7621: increase PERST_DELAY_MS
Date: Mon, 21 Nov 2022 16:50:52 -0600 [thread overview]
Message-ID: <20221121225052.GA140064@bhelgaas> (raw)
In-Reply-To: <CAMhs-H-i1arxS4daudfG8AGuFyxmJuNe6CY4A+Pi+u8RNUM65A@mail.gmail.com>
On Sun, Nov 20, 2022 at 08:37:50AM +0100, Sergio Paracuellos wrote:
> On Sat, Nov 19, 2022 at 7:03 PM Bjorn Helgaas <helgaas@kernel.org> wrote:
> > On Sat, Nov 19, 2022 at 12:08:37PM +0100, Sergio Paracuellos wrote:
> > > Some devices using this SoC and PCI's like ZBT WE1326 and Netgear R6220 need
> > > more time to get the PCI ports properly working after reset. Hence, increase
> > > PERST_DELAY_MS definition used for this purpose from 100 ms to 500 ms to get
> > > into confiable boots and working PCI for these devices.
> >
> > confiable?
>
> It seems my spanish confused my mind here :). I meant trustable.
Your English is WAY, WAY better than my Spanish :)
I assume this is more about just making boots more "reliable" than
something like the "Trusted Boot" or "Secure Boot" technologies [1,2]?
Bjorn
[1] https://trustedcomputinggroup.org/resource/trusted-boot/
[2] https://learn.microsoft.com/en-us/windows/security/trusted-boot
next prev parent reply other threads:[~2022-11-21 22:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 11:08 [PATCH] PCI: mt7621: increase PERST_DELAY_MS Sergio Paracuellos
2022-11-19 18:03 ` Bjorn Helgaas
2022-11-20 7:37 ` Sergio Paracuellos
2022-11-21 22:50 ` Bjorn Helgaas [this message]
2022-11-22 6:50 ` 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=20221121225052.GA140064@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=robh@kernel.org \
--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