From patchwork Sat Oct 9 16:05:35 2021 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Hans de Goede X-Patchwork-Id: 12547789 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id EE4A2C433F5 for ; Sat, 9 Oct 2021 16:06:04 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D236460FC1 for ; Sat, 9 Oct 2021 16:06:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229471AbhJIQIA (ORCPT ); Sat, 9 Oct 2021 12:08:00 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:31082 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229518AbhJIQIA (ORCPT ); Sat, 9 Oct 2021 12:08:00 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1633795562; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=iaPvDQL8oAOCDALj9mcU71yczG7rgFT9+NpjQN32tLo=; b=fwksu5hJvG+ogu8Gpi0Y0XhHnckUd9aohnh4fZmgwyYhGOAmOFEUfIdgP8AUGKNrsLGIsm TNKdRKaCzc49s+CSzKKM8GhcWanTY91BTgMHAl/tUYp8OmAOvjd2hv3S9VsG67TyMIB4Gk in8zNAcLNuXmaiIqKWQj0DAr7MalWI8= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-534-JhZfooeOOti73xzA8008KA-1; Sat, 09 Oct 2021 12:06:00 -0400 X-MC-Unique: JhZfooeOOti73xzA8008KA-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 6ED181808304; Sat, 9 Oct 2021 16:05:58 +0000 (UTC) Received: from x1.localdomain.com (unknown [10.39.192.7]) by smtp.corp.redhat.com (Postfix) with ESMTP id 1C9F15C1B4; Sat, 9 Oct 2021 16:05:48 +0000 (UTC) From: Hans de Goede To: "Rafael J . Wysocki" , Mark Gross , Andy Shevchenko , Daniel Scally , Laurent Pinchart , Mauro Carvalho Chehab , Liam Girdwood , Mark Brown , Michael Turquette , Stephen Boyd Cc: Hans de Goede , Len Brown , linux-acpi@vger.kernel.org, platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org, Sakari Ailus , Kate Hsuan , linux-media@vger.kernel.org, linux-clk@vger.kernel.org Subject: [PATCH v2 00/13] Add support for X86/ACPI camera sensor/PMIC setup with clk and regulator platform data Date: Sat, 9 Oct 2021 18:05:35 +0200 Message-Id: <20211009160548.306550-1-hdegoede@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 Precedence: bulk List-ID: X-Mailing-List: linux-clk@vger.kernel.org Hi All, Here is v2 of my patch-set adding support for camera sensor connected to a TPS68470 PMIC on x86/ACPI devices. The big change in v2 is that I've reworked how to defer the binding of the camera-sensor drivers till all clk/regulator/gpio consumer/lookup info has been registered. See the new patch 1 + 2 (replacing the old patch 1 - 3) in this version. There are also some small other changes, mostly as a result of this change and patch 12 + 13 are new patches. ### The clk and regulator frameworks expect clk/regulator consumer-devices to have info about the consumed clks/regulators described in the device's fw_node, but on ACPI this info is missing. This series worksaround this by providing platform_data with the info to the TPS68470 clk/regulator MFD cells. Patches 1 - 2 + 13 deal with a probe-ordering problem this introduces, since the lookups are only registered when the provider-driver binds, trying to get these clks/regulators before then results in a -ENOENT error for clks and a dummy regulator for regulators. See the patches for more details. Patch 3 adds a header file which adds tps68470_clk_platform_data and tps68470_regulator_platform_data structs. The futher patches depend on this new header file. Patch 4 + 5 add the TPS68470 clk and regulator drivers Patches 6 - 11 Modify the INT3472 driver which instantiates the MFD cells to provide the necessary platform-data. Assuming this series is acceptable to everyone, we need to talk about how to merge this. Patches 1 + 2 can be merged into linux-pm by Rafael, independent of the rest of the series. For "[PATCH 03/13] platform_data: Add linux/platform_data/tps68470.h file", which all further patches depend on I plan to provide an immutable branch myself (once it has been reviewed), which the clk / regulator maintainers can then merge before merging the clk / regulator driver which depends on this. And patches 12 + 13 can be merged independently into the media tree. Regards, Hans Daniel Scally (2): platform/x86: int3472: Enable I2c daisy chain media: ipu3-cio2: Add INT347A to cio2-bridge Hans de Goede (11): ACPI: Add a honor_deps flag to struct acpi_device ACPI: honor dependencies for devices with a _DEP pointing to an INT3472 device platform_data: Add linux/platform_data/tps68470.h file regulator: Introduce tps68470-regulator driver clk: Introduce clk-tps68470 driver platform/x86: int3472: Split into 2 drivers platform/x86: int3472: Add get_sensor_adev_and_name() helper platform/x86: int3472: Pass tps68470_clk_platform_data to the tps68470-regulator MFD-cell platform/x86: int3472: Pass tps68470_regulator_platform_data to the tps68470-regulator MFD-cell platform/x86: int3472: Deal with probe ordering issues media: ipu3-cio2: Add module soft-deps for the INT3472 drivers drivers/acpi/bus.c | 4 +- drivers/acpi/scan.c | 20 +- drivers/clk/Kconfig | 6 + drivers/clk/Makefile | 1 + drivers/clk/clk-tps68470.c | 256 ++++++++++++++++++ drivers/media/pci/intel/ipu3/cio2-bridge.c | 2 + drivers/media/pci/intel/ipu3/ipu3-cio2-main.c | 6 + drivers/platform/x86/intel/int3472/Makefile | 9 +- ...lk_and_regulator.c => clk_and_regulator.c} | 2 +- drivers/platform/x86/intel/int3472/common.c | 82 ++++++ .../{intel_skl_int3472_common.h => common.h} | 6 +- ...ntel_skl_int3472_discrete.c => discrete.c} | 51 ++-- .../intel/int3472/intel_skl_int3472_common.c | 106 -------- ...ntel_skl_int3472_tps68470.c => tps68470.c} | 97 ++++++- drivers/platform/x86/intel/int3472/tps68470.h | 25 ++ .../x86/intel/int3472/tps68470_board_data.c | 118 ++++++++ drivers/regulator/Kconfig | 9 + drivers/regulator/Makefile | 1 + drivers/regulator/tps68470-regulator.c | 193 +++++++++++++ include/acpi/acpi_bus.h | 2 + include/linux/mfd/tps68470.h | 11 + include/linux/platform_data/tps68470.h | 35 +++ 22 files changed, 892 insertions(+), 150 deletions(-) create mode 100644 drivers/clk/clk-tps68470.c rename drivers/platform/x86/intel/int3472/{intel_skl_int3472_clk_and_regulator.c => clk_and_regulator.c} (99%) create mode 100644 drivers/platform/x86/intel/int3472/common.c rename drivers/platform/x86/intel/int3472/{intel_skl_int3472_common.h => common.h} (94%) rename drivers/platform/x86/intel/int3472/{intel_skl_int3472_discrete.c => discrete.c} (91%) delete mode 100644 drivers/platform/x86/intel/int3472/intel_skl_int3472_common.c rename drivers/platform/x86/intel/int3472/{intel_skl_int3472_tps68470.c => tps68470.c} (55%) create mode 100644 drivers/platform/x86/intel/int3472/tps68470.h create mode 100644 drivers/platform/x86/intel/int3472/tps68470_board_data.c create mode 100644 drivers/regulator/tps68470-regulator.c create mode 100644 include/linux/platform_data/tps68470.h