From: Hans de Goede <hdegoede@redhat.com>
To: Punit Agrawal <punit1.agrawal@toshiba.co.jp>
Cc: linux-serial@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, nobuhiro1.iwamatsu@toshiba.co.jp,
shrirang.bagul@canonical.com, stable@vger.kernel.org,
Rob Herring <robh@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Johan Hovold <johan@kernel.org>
Subject: Re: [PATCH] serdev: Don't claim unsupported serial devices
Date: Thu, 19 Dec 2019 09:30:38 +0100 [thread overview]
Message-ID: <a2e86d54-287a-16b4-3dac-9e3fe3dee753@redhat.com> (raw)
In-Reply-To: <87eex1noak.fsf@kokedama.swc.toshiba.co.jp>
Hi,
On 19-12-2019 01:37, Punit Agrawal wrote:
> Hans de Goede <hdegoede@redhat.com> writes:
>
>> Hi,
>>
>> On 18-12-2019 07:56, Punit Agrawal wrote:
>>> Serdev sub-system claims all serial devices that are not already
>>> enumerated. As a result, no device node is created for serial port on
>>> certain boards such as the Apollo Lake based UP2. This has the
>>> unintended consequence of not being able to raise the login prompt via
>>> serial connection.
>>>
>>> Introduce a blacklist to reject devices that should not be treated as
>>> a serdev device. Add the Intel HS UART peripheral ids to the blacklist
>>> to bring back serial port on SoCs carrying them.
>>>
>>> Cc: stable@vger.kernel.org
>>> Signed-off-by: Punit Agrawal <punit1.agrawal@toshiba.co.jp>
>>> Cc: Rob Herring <robh@kernel.org>
>>> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>>> Cc: Johan Hovold <johan@kernel.org>
>>> Cc: Hans de Goede <hdegoede@redhat.com>
>>
>> Thank you for addressing this long standing issue.
>
> I am surprised there hasn't been more people complaining! Maybe even on
> x86 mainline isn't that widely used on development boards.
I think it is also a case of there not being that manu x86 development
boards.
Regards,
Hans
prev parent reply other threads:[~2019-12-19 8:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 6:56 [PATCH] serdev: Don't claim unsupported serial devices Punit Agrawal
2019-12-18 8:10 ` Greg Kroah-Hartman
2019-12-18 8:22 ` Punit Agrawal
2019-12-18 8:56 ` Johan Hovold
2019-12-18 9:09 ` Punit Agrawal
2019-12-19 8:39 ` Rafael J. Wysocki
2019-12-19 8:51 ` Johan Hovold
2019-12-19 8:58 ` Punit Agrawal
2019-12-18 10:05 ` Hans de Goede
2019-12-19 0:37 ` Punit Agrawal
2019-12-19 8:30 ` Hans de Goede [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=a2e86d54-287a-16b4-3dac-9e3fe3dee753@redhat.com \
--to=hdegoede@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=punit1.agrawal@toshiba.co.jp \
--cc=robh@kernel.org \
--cc=shrirang.bagul@canonical.com \
--cc=stable@vger.kernel.org \
/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).