Received: by 2002:a05:6a10:6744:0:0:0:0 with SMTP id w4csp338954pxu; Thu, 15 Oct 2020 05:26:37 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzgB64/T2fNt7xthMeVx2IOSQg9g7HnTWsJNUr0wxLTdWqRiv/g6AfOwi4qNzM3jLjmnUwX X-Received: by 2002:a17:906:38d8:: with SMTP id r24mr1683371ejd.32.1602764796968; Thu, 15 Oct 2020 05:26:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1602764796; cv=none; d=google.com; s=arc-20160816; b=nvtQyYjMoB0qVKYd3aavPBGkvYlYl8z56Y0wtFtuw7AKwjKWCw/UPm9oKWF9waLnUB K9DiJ3aaagg/3Gh3yZp1M5roPCOAW0nW1QBPpo0CcYvkNT3rcZUrdlJwtmCDYYlosxxH atCEzQ94KbSNuRSTxUL44LkMaBR4nv7srZB14ULz1NSll3YLc28xxNzvwMK8n/JNU4Hz kLkN9z0ujiFIn9xGYz1T0O08/X+3fTA2slLgwdsBf+i0/V5VLj3uYKcCRdOIHPTB+lVI W39zjpH1u+8ZSd4RGFtzbS1mZ44DIpgMfAVtvx9+Zufn7OYmwCZDWUj3CsbI9ONLPI+d Z0fQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from; bh=JPbf/Di45eD8kS4rH49J1mqPk3C/17tRTryyv3J001o=; b=DcyncLYL2IeDivlfNJMr7qaAXs6k6XypHkm5okECPfuQVivphb5/YOk50hdYVlKjBy dz+bTGo59uBvNY/VHLbHQORa/Ra+ooxwS5R2KGy9MLZf4oNB7N5Ok+ui7RHfZSUX3fJn g09Xha3DRGMUd5b/qqTbG5y0UfjmfFWUzChu602C4tVHmAOMO0iT2wNi48YeJKi9/Kmx 3oMFqYfXum4GpZrsy2fvWi6OOHLLNee8oX55a1pTRuSIo989Y2hQE8Qyd81Xk/HBBpdn 0fsguJX6Zo+8EB8WKkMJJaqSEaU0MuvWV6hHIR5R5S1atgYuZFbdt0UQDZEzFk1g5cuU jn7Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id u18si2116963edf.140.2020.10.15.05.26.11; Thu, 15 Oct 2020 05:26:36 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729935AbgJOLn5 (ORCPT + 99 others); Thu, 15 Oct 2020 07:43:57 -0400 Received: from mx2.suse.de ([195.135.220.15]:48372 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727923AbgJOLn5 (ORCPT ); Thu, 15 Oct 2020 07:43:57 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 52F4EABBE; Thu, 15 Oct 2020 11:43:56 +0000 (UTC) From: Nicolas Saenz Julienne To: gregkh@linuxfoundation.org, rafael.j.wysocki@intel.com, Rob Herring , Frank Rowand Cc: f.fainelli@gmail.com, linux-rpi-kernel@lists.infradead.org, saravanak@google.com, u.kleine-koenig@pengutronix.de, Nicolas Saenz Julienne , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [RFC] of/platform: Create device link between simple-mfd and its children Date: Thu, 15 Oct 2020 13:43:46 +0200 Message-Id: <20201015114346.15743-1-nsaenzjulienne@suse.de> X-Mailer: git-send-email 2.28.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 'simple-mfd' usage implies there might be some kind of resource sharing between the parent device and its children. By creating a device link with DL_FLAG_AUTOREMOVE_CONSUMER we make sure that at no point in time the parent device is unbound while leaving its children unaware that some of their resources disappeared. Signed-off-by: Nicolas Saenz Julienne --- Some questions: - To what extent do we care about cleanly unbinding platform devices at runtime? My rationale here is: "It's a platform device, for all you know you might be unbinding someting essential to the system. So if you're doing it, you better know what you're doing." - Would this be an abuse of device links? - If applying this to all simple-mfd devices is a bit too much, would this be acceptable for a specific device setup. For example RPi4's firmware interface (simple-mfd user) is passed to consumer drivers trough a custom API (see rpi_firmware_get()). So, when unbound, consumers are left with a firmware handle that points to nothing. drivers/of/platform.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/drivers/of/platform.c b/drivers/of/platform.c index b557a0fcd4ba..8d5b55b81764 100644 --- a/drivers/of/platform.c +++ b/drivers/of/platform.c @@ -390,8 +390,14 @@ static int of_platform_bus_create(struct device_node *bus, } dev = of_platform_device_create_pdata(bus, bus_id, platform_data, parent); - if (!dev || !of_match_node(matches, bus)) - return 0; + if (!dev) + return 0; + + if (parent && of_device_is_compatible(parent->of_node, "simple-mfd")) + device_link_add(&dev->dev, parent, DL_FLAG_AUTOREMOVE_CONSUMER); + + if (!of_match_node(matches, bus)) + return 0; for_each_child_of_node(bus, child) { pr_debug(" create child: %pOF\n", child); -- 2.28.0