linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Punit Agrawal <punit1.agrawal@toshiba.co.jp>
To: Johan Hovold <johan@kernel.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	<linux-serial@vger.kernel.org>,
	"ACPI Devel Maling List" <linux-acpi@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	<nobuhiro1.iwamatsu@toshiba.co.jp>,
	<shrirang.bagul@canonical.com>, Stable <stable@vger.kernel.org>,
	Rob Herring <robh@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Hans de Goede" <hdegoede@redhat.com>
Subject: Re: [PATCH] serdev: Don't claim unsupported serial devices
Date: Thu, 19 Dec 2019 17:58:08 +0900	[thread overview]
Message-ID: <875zicofof.fsf@kokedama.swc.toshiba.co.jp> (raw)
In-Reply-To: <20191219085114.GQ22665@localhost> (Johan Hovold's message of "Thu, 19 Dec 2019 09:51:14 +0100")

Johan Hovold <johan@kernel.org> writes:

> On Thu, Dec 19, 2019 at 09:39:57AM +0100, Rafael J. Wysocki wrote:
>> On Wed, Dec 18, 2019 at 9:56 AM Johan Hovold <johan@kernel.org> wrote:
>> >
>> > On Wed, Dec 18, 2019 at 03:56:46PM +0900, 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>
>> > > ---
>> > >
>> > > Hi,
>> > >
>> > > The patch has been updated based on feedback recieved on the RFC[0].
>> > >
>> > > Please consider merging if there are no objections.
>> >
>> > Rafael, I vaguely remember you arguing for a white list when we
>> > discussed this at some conference. Do you have any objections to the
>> > blacklist approach taken here?
>> 
>> As a rule, I prefer whitelisting, because it only enables the feature
>> for systems where it has been tested and confirmed to work.
>> 
>> However, if you are convinced that in this particular case the feature
>> should work on the vast majority of systems with a few possible
>> exceptions, blacklisting is fine too.
>> 
>> It all depends on what the majority is, at least in principle.
>
> Ok, thanks. I don't have a preference either way in this case simply
> because I don't know the distribution you refer to.
>
> But if Hans thinks blacklisting is the way to go then let's do that. We
> haven't had that many reports about this, but if that were to change
> down the line, I guess we can always switch to whitelisting.
>
> Punit, feel free to add my
>
> Acked-by: Johan Hovold <johan@kernel.org>
>
> after addressing the review comments you've gotten so far.

Thanks Johan.

I will post a new version with the updates and acks.

  reply	other threads:[~2019-12-19  8:57 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 [this message]
2019-12-18 10:05 ` Hans de Goede
2019-12-19  0:37   ` Punit Agrawal
2019-12-19  8:30     ` Hans de Goede

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=875zicofof.fsf@kokedama.swc.toshiba.co.jp \
    --to=punit1.agrawal@toshiba.co.jp \
    --cc=gregkh@linuxfoundation.org \
    --cc=hdegoede@redhat.com \
    --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=rafael.j.wysocki@intel.com \
    --cc=rafael@kernel.org \
    --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).