From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A131D3D75C4; Wed, 4 Mar 2026 18:46:49 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772650009; cv=none; b=pvDPPcnK8LaYrvyegGdD2MeeqY0BBiOeKPSecsoXML0lMqTiX0hgP1huzNnSTSj6JsDRtcjrDWFhjxS1DVWOdp50uUVIoNqdQ/TlcMWcz5oo7O82lhtDuqyeTwiGasZepRXrz60q+IZgf8wz8Kl7jT98mE1z3z8lBtFALGyAzSM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772650009; c=relaxed/simple; bh=JcSKSxzdPzOErYA+1dovArclnNI+XLgbFAD5iZnDgSk=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type; b=ZTy04ciYhPIPjbgKkd/Hdj2yYRzNs5n1GHcVi/22da/NraVD/TsIk58x5uKJqELweJy+mBrx5nLtYVvBpp+MBBOaivzmey8trsOmZRVvfvnx6bLw8aLabKOT9JiL4Pd3IV8T5t+eIc9eFVYF3zlekQObt0ZMP+MqRMFAKWnh7Io= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=rTbHOdJF; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="rTbHOdJF" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 97567C19425; Wed, 4 Mar 2026 18:46:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1772650009; bh=JcSKSxzdPzOErYA+1dovArclnNI+XLgbFAD5iZnDgSk=; h=From:To:Cc:Subject:Date:From; b=rTbHOdJFDMFKv5mpphumlif/prEFG5ImwIwKoSUvOqRLiIw7P8FA0jl/AsetWFTbY sJiFtcGhuy7kAOKbktDopEsfYWQ/bHo4Squ9LWPgk0K6ygX1hao65qe18Roww79Wos M6kP36iNLpe+/of0KLXNj+1wBE8aYR2e9bQiwF4d7nHOx5kQPQ/6jaN5GH8EgARm3U y5J/d2iDXjoH4OZYMPBHIyVoaUapZDX+V8f3ny8XlavzF7OTriTCmnJuLkg1r4vYUR B23dJ0jMpa8J21KbuzDsSI4qzdMiuG5c6MvHt69kBVfkFjEDmDU42o7QtSUTINb45L d6PPid3rUvwrw== From: "Rafael J. Wysocki" To: chrome-platform@lists.linux.dev Cc: LKML , Linux ACPI , Benson Leung , Tzung-Bi Shih , Enric Balletbo i Serra , Ravi Chandra Sadineni Subject: [PATCH v1 0/6] platform/chrome: Bind drivers to platform devices instead of ACPI ones Date: Wed, 04 Mar 2026 19:41:39 +0100 Message-ID: <2274474.Mh6RI2rZIc@rafael.j.wysocki> Organization: Linux Kernel Development Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" Hi All, This series is part of a larger effort to switch over all drivers using the struct acpi_driver interface to the more common struct platform_driver interface and eliminate the former. The background is explained in Documentation/driver-api/acpi/acpi-drivers.rst and in the changelog of the patch that introduced the above document: https://lore.kernel.org/all/2396510.ElGaqSPkdT@rafael.j.wysocki/ The bottom line is that the kernel would be better off without struct acpi_driver and so it is better to get rid of it. This series carries out driver conversions of Chrome platform drivers. Patche [1/6] converts the ChromeOS privacy screen driver to using struct platform_driver for device binding. Patche [2/6] fixes a wakeup source object leak on remove in the chromeos_tbmc driver. Patch [3/6] updates the chromeos_tbmc driver to install an ACPI notify handler by itself instead of using the .notify() callback from struct acpi_driver, which is requisite for the driver conversion. Patche [4/6] converts the chromeos_tbmc driver to using struct platform_driver for device binding. Patch [5/6] updates the wilco_ec-event driver to install an ACPI notify handler by itself instead of using the .notify() callback from struct acpi_driver, which is requisite for the driver conversion. Patche [6/6] converts the wilco_ec-event driver to using struct platform_driver for device binding. Thanks!