From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [PATCH v2 9/9] Bluetooth: hci_bcm: Add (runtime)pm support to the serdev driver To: Marcel Holtmann Cc: "Gustavo F. Padovan" , Johan Hedberg , =?UTF-8?Q?Fr=c3=a9d=c3=a9ric_Danis?= , Sebastian Reichel , robh@kernel.org, linux-bluetooth@vger.kernel.org, linux-serial@vger.kernel.org, linux-acpi@vger.kernel.org References: <20171004184343.7855-1-hdegoede@redhat.com> <20171004184343.7855-9-hdegoede@redhat.com> From: Hans de Goede Message-ID: <1389d64c-17aa-c6a1-d56f-6c2fe877f247@redhat.com> Date: Thu, 5 Oct 2017 13:18:38 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed List-ID: Hi, On 05-10-17 12:45, Marcel Holtmann wrote: > Hi Hans, > >> Make the serdev driver use struct bcm_device as its driver data and share >> all the pm / GPIO / IRQ related code paths with the platform driver. >> >> After this commit the 2 drivers are in essence the same and the serdev >> driver interface can be used for all ACPI enumerated HCI UARTs. >> >> Signed-off-by: Hans de Goede >> --- >> drivers/bluetooth/hci_bcm.c | 118 +++++++++++++++++++++++++------------------- >> 1 file changed, 68 insertions(+), 50 deletions(-) > > all 9 patches have been applied to bluetooth-next tree. Excellent, thank you! So I guess this means we can also move forward with getting the 2 patches from Frédéric Danis merged ? There is a bit of a bisect-ability problem there, if the acpi pull-req gets merged first then uart attached bcm bt will stop working until the bluetooth subsys is also merged. But I don't think this will impact a lot of users (also given the need for a manual btattach so far), so I don't think this is a big problem... ? Regards, Hans