From: Alexey Kardashevskiy <aik@amd.com>
To: linux-pci@vger.kernel.org
Cc: "Martin Mareš" <mj@ucw.cz>
Subject: Re: [PATCH pciutils] ls-ecaps: Correct IDE link state reporting
Date: Mon, 15 Apr 2024 12:22:37 +1000 [thread overview]
Message-ID: <af689b1f-43bb-403e-9de1-e6c43f398662@amd.com> (raw)
In-Reply-To: <20240411042844.2241434-1-aik@amd.com>
I found more inconsistencies so v2 will come soon. Sorry for the noise.
Thanks,
On 11/4/24 14:28, Alexey Kardashevskiy wrote:
> PCIe r6.0, sec 7.9.26.4.2 "Link IDE Stream Status Register defines"
> the link state as:
>
> 0000b Insecure
> 0010b Secure
>
> The same definition applies to selective streams as well.
> The existing code wrongly assumes "secure" is 0001b, fix that for both
> link and selective streams.
>
> Fixes: 42fc4263ec0e ("ls-ecaps: Add decode support for IDE Extended Capability")
> Signed-off-by: Alexey Kardashevskiy <aik@amd.com>
> ---
> ls-ecaps.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/ls-ecaps.c b/ls-ecaps.c
> index b40ba72..5c2724e 100644
> --- a/ls-ecaps.c
> +++ b/ls-ecaps.c
> @@ -1512,7 +1512,7 @@ static void
> cap_ide(struct device *d, int where)
> {
> const char *hdr_enc_mode[] = { "no", "17:2", "25:2", "33:2", "41:2" };
> - const char *stream_state[] = { "insecure", "secure" };
> + const char *stream_state[] = { "insecure", "reserved", "secure" };
> const char *aggr[] = { "-", "=2", "=4", "=8" };
> u32 l, l2, linknum = 0, selnum = 0, addrnum, off, i, j;
> char buf1[16], buf2[16], offs[16];
--
Alexey
prev parent reply other threads:[~2024-04-15 2:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 4:28 [PATCH pciutils] ls-ecaps: Correct IDE link state reporting Alexey Kardashevskiy
2024-04-15 2:22 ` Alexey Kardashevskiy [this message]
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=af689b1f-43bb-403e-9de1-e6c43f398662@amd.com \
--to=aik@amd.com \
--cc=linux-pci@vger.kernel.org \
--cc=mj@ucw.cz \
/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