From: Tony Lindgren <tony@atomide.com>
To: Matthew Howell <matthew.howell@sealevel.com>
Cc: gregkh@linuxfoundation.org, linux-serial@vger.kernel.org,
ryan.wenglarz@sealevel.com, james.olson@sealevel.com
Subject: Re: [PATCH] serial: Revert serial: core: Fix serial core port id to not use port->line
Date: Tue, 29 Aug 2023 06:52:45 +0300 [thread overview]
Message-ID: <20230829035245.GF11662@atomide.com> (raw)
In-Reply-To: <98a891fd-5a1f-6568-a12c-28577126a42@sealevel.com>
Hi,
* Matthew Howell <matthew.howell@sealevel.com> [230828 20:41]:
> From: Matthew Howell <matthew.howell@sealevel.com>
> XR17V35X cards seemingly unable to register serial port. Confirmed on
> Sealevel 7202C, 7204EC, and Exar XR17V352 reference board.
> dmesg states: "Couldn't register serial port 0, irq 24, type 2, error -22"
>
> I first identified the problem when I pulled down 6.6-rc1 and I was able
> to trace it to d962de6ae51f9b76ad736220077cda83084090b1. I understand that this
> commit is noted as being reverted in 1ef2c2df1199, but I was only able to
> resolve the issue by reverting d962de6ae51f myself using this patch.
Thanks for the report. Do you maybe mean 6.5-rc1 instead of 6.6-rc1 above?
If so, I suspect the issue you are reporting got already fixed during the
-rc cycle for v6.5 kernel.
> I suggest reverting using this patch unless someone more knowledgeable
> about what these changes actually do has a better suggestion.
Can you please test with v6.5 kernel? It has the two fixes below that
sounds like you may have been missing:
a4a79e03bab5 ("serial: core: Revert port_id use")
04c7f60ca477 ("serial: core: Fix serial core port id, including multiport devices")
Note how commit a4a79e03bab5 already did a partial revert of what you're
suggesting.
If you already have these two commits, then let's investigate further to
see what might be still wrong.
Regards,
Tony
next prev parent reply other threads:[~2023-08-29 3:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 20:41 [PATCH] serial: Revert serial: core: Fix serial core port id to not use port->line Matthew Howell
2023-08-29 3:52 ` Tony Lindgren [this message]
2023-08-29 13:42 ` Matthew Howell
2023-08-29 20:15 ` Tony Lindgren
2023-08-31 14:58 ` Matthew Howell
2023-09-01 4:47 ` Tony Lindgren
2023-09-01 18:48 ` Matthew Howell
2023-09-02 4:34 ` Tony Lindgren
[not found] ` <c4b1db31-7814-0d22-36de-a7e6f117d89c@sealevel.com>
2023-09-05 15:55 ` Tony Lindgren
2023-09-05 16:43 ` Matthew Howell
2023-09-05 16:51 ` Tony Lindgren
2023-09-11 13:04 ` Matthew Howell
2023-09-11 13:15 ` Greg KH
2023-09-11 13:58 ` Matthew Howell
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=20230829035245.GF11662@atomide.com \
--to=tony@atomide.com \
--cc=gregkh@linuxfoundation.org \
--cc=james.olson@sealevel.com \
--cc=linux-serial@vger.kernel.org \
--cc=matthew.howell@sealevel.com \
--cc=ryan.wenglarz@sealevel.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