Return-Path: MIME-Version: 1.0 Sender: rjwysocki@gmail.com In-Reply-To: References: <1507107090-15992-1-git-send-email-frederic.danis.oss@gmail.com> <1507107090-15992-2-git-send-email-frederic.danis.oss@gmail.com> From: "Rafael J. Wysocki" Date: Sat, 7 Oct 2017 02:03:25 +0200 Message-ID: Subject: Re: [PATCH 1/2] serdev: Add ACPI support To: Marcel Holtmann Cc: Rob Herring , =?UTF-8?B?RnLDqWTDqXJpYyBEYW5pcw==?= , Sebastian Reichel , Loic Poulain , Johan Hovold , Lukas Wunner , Hans de Goede , Greg Kroah-Hartman , "open list:BLUETOOTH DRIVERS" , "linux-serial@vger.kernel.org" , "linux-acpi@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" List-ID: On Fri, Oct 6, 2017 at 8:32 PM, Marcel Holtmann wrote= : > Hi Rob, > >>> This patch allows SerDev module to manage serial devices declared as >>> attached to an UART in ACPI table. >>> >>> acpi_serdev_add_device() callback will only take into account entries >>> without enumerated flag set. This flags is set for all entries during >>> ACPI scan, except for SPI and I2C serial devices, and for UART with >>> 2nd patch in the series. >>> >>> Signed-off-by: Fr=C3=A9d=C3=A9ric Danis >>> --- >>> drivers/tty/serdev/core.c | 99 ++++++++++++++++++++++++++++++++++++++++= ++++--- >>> 1 file changed, 94 insertions(+), 5 deletions(-) >> >> Reviewed-by: Rob Herring > > so how do we get these changes upstream? If the serdev changes alone do n= ot cause any harm, I am almost proposing taking them through bluetooth-next= tree and only leave only the ACPI change to the ACPI maintainers. That would be fine by me. I can take the serdev patch too, though. Thanks, Rafael