From: Johan Hovold <johan@kernel.org>
To: Greg Kroah-Hartman <greg@kroah.com>
Cc: "Frédéric Danis" <frederic.danis.oss@gmail.com>,
"Marcel Holtmann" <marcel@holtmann.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Johan Hovold" <johan@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Sebastian Reichel" <sre@kernel.org>,
"Loic Poulain" <loic.poulain@gmail.com>,
"Lukas Wunner" <lukas@wunner.de>,
"Hans de Goede" <hdegoede@redhat.com>,
"open list:BLUETOOTH DRIVERS" <linux-bluetooth@vger.kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"ACPI Devel Maling List" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH v3 0/2] ACPI serdev support
Date: Thu, 19 Oct 2017 16:23:54 +0200 [thread overview]
Message-ID: <20171019142354.GE5638@localhost> (raw)
In-Reply-To: <20171018145608.GB27138@kroah.com>
On Wed, Oct 18, 2017 at 04:56:08PM +0200, Greg Kroah-Hartman wrote:
> On Wed, Oct 18, 2017 at 04:46:05PM +0200, Frédéric Danis wrote:
> > Le 11/10/2017 à 20:32, Marcel Holtmann a écrit :
> > > > > > Add ACPI support for serial attached devices.
> > > > > >
> > > > > > Currently, serial devices are not set as enumerated during
> > > > > > ACPI scan for SPI or i2c buses (but not for UART). This
> > > > > > should also be done for UART serial devices. I renamed
> > > > > > *spi_i2c_slave* to *serial_bus_slave* to reflect this.
> > > > > >
> > > > > > This needs Johan Hovold's "serdev: fix registration of
> > > > > > second slave" patch.
> > > > > In theory this series could go in through the acpi-tree
> > > > > without my fix. It would only affect an error case where an
> > > > > unlikely failure to register an ACPI serdev device, would
> > > > > prevent the tty-class device from being registered instead of
> > > > > the controller. That is, something we can live with until this
> > > > > all converges in 4.15-rc1 if needed.
> > > > >
> > > > > That said, I think we should consider taking all serdev
> > > > > changes, and therefore also the ACPI patch, through the tty
> > > > > tree instead in order to avoid merge conflicts. Rafael?
> > > > OK
> > > >
> > > > Please feel free to add
> > > >
> > > > Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> > > >
> > > > to the ACPI core change.
> > > >
> > > > And I will assume that this series will go in via the tty tree.
> > > you have to take these two patches now via the TTY tree now. In
> > > case you already marked them as someone else problem ;)
> > Is there any problem I missed with those patches?
> > Do I have to re-send them?
>
> No, they are in my queue, still catching up...
I just realised that we cannot merge this series (the second acpi patch)
until the hci_intel driver gains serdev support or otherwise PM will
break for those devices.
Specifically, the hci_intel driver uses similar hacks as the hci_bcm
driver does for PM, so we need something like Hans's hci_bcm series also
for hci_intel before we can do the switch.
Hopefully there are no more of these...
Johan
next prev parent reply other threads:[~2017-10-19 14:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 8:32 [PATCH v3 0/2] ACPI serdev support Frédéric Danis
2017-10-11 8:32 ` [PATCH v3 1/2] serdev: Add ACPI support Frédéric Danis
2017-10-11 8:43 ` Johan Hovold
2017-10-11 8:32 ` [PATCH v3 2/2] ACPI / scan: Fix enumeration for special UART devices Frédéric Danis
2017-10-15 9:57 ` Lukas Wunner
2018-01-31 14:21 ` [v3,2/2] " Graeme Gregory
2018-02-02 10:03 ` Frédéric Danis
2018-02-02 15:28 ` Graeme Gregory
2017-10-11 9:03 ` [PATCH v3 0/2] ACPI serdev support Johan Hovold
2017-10-11 13:09 ` Rafael J. Wysocki
2017-10-11 18:32 ` Marcel Holtmann
2017-10-18 14:46 ` Frédéric Danis
2017-10-18 14:56 ` Greg Kroah-Hartman
2017-10-19 14:23 ` Johan Hovold [this message]
2017-10-19 14:26 ` Hans de Goede
2017-10-19 14:32 ` Marcel Holtmann
2017-10-19 14:56 ` Hans de Goede
2017-10-19 16:15 ` Loic Poulain
2017-10-19 18:50 ` Hans de Goede
2017-10-19 19:00 ` Marcel Holtmann
2017-10-19 19:05 ` Hans de Goede
2017-10-21 9:59 ` Johan Hovold
2017-10-19 14:32 ` Johan Hovold
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=20171019142354.GE5638@localhost \
--to=johan@kernel.org \
--cc=frederic.danis.oss@gmail.com \
--cc=greg@kroah.com \
--cc=hdegoede@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=loic.poulain@gmail.com \
--cc=lukas@wunner.de \
--cc=marcel@holtmann.org \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=sre@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).