Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp7224457imu; Thu, 31 Jan 2019 07:00:43 -0800 (PST) X-Google-Smtp-Source: ALg8bN5MSLvAbZFopH5Qf5nSkwhN8FY08lahY7IJkzyzqQwwo7xqeqZkqFJ7cghjUiWlYX37L2qL X-Received: by 2002:a17:902:30a3:: with SMTP id v32mr35585807plb.26.1548946843075; Thu, 31 Jan 2019 07:00:43 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548946843; cv=none; d=google.com; s=arc-20160816; b=pUOeewqQCNSQfkxNNMkvqq3HTY5p/51sqraVUpXgs1qAVPlYDUIg6J3J3/kjeoHMj5 44+q8AY1QIxHlN6/GoW7TNySSRjibnSEhiNV/qV92DdS1mtbhGx4ZxHfVFw8VCRU8K+9 kRKgBwJuPa4n/+yYXQp34+A1Qu+GnDrkVNoPV8SYqZRDKem7HCLUF4Od9fm3s0YGx8V1 gerwUyX8B8pamYgq8ZpS41sJjo/jdmFUAA5A6S64ZbwcEQ4OCNZkpV5MifGHL9Vke7Ex 1t4gZJ41jam7vRFI9876++Whwb0ZWu11/yPFY30EA1+I4nr85lls7/UuT/7JIPwQqd6J PmkA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=kaGmse/o4tAPSO+AtMBVyQZx7oFQ4O6B+YYXQzR/2nU=; b=Ytm5BEKAA4452uKEMkOKjRYQs+YtSfR4mPNUWcb2a3QbL3MmHpMWM5e0Y0Z7Iei5Dv oOpi7JPr0zAPNw+dbxecI/fLnURofcct4C4JFgp2xPZvl8Pv3MbrIjLssOq/0NuKRU5o f9lcT8bp40YC/w1yJi3zB7oYfEJvDs+7Mr7CBZSPHfN1GhLMDMFf+5WlXdNt6y2FMLwV G3uLs4ctMZAdARKjaWNhQMH5kmHaRPXskxVkPGm/CEbXp1WO5X8eA5/UyvOo5DKc/Kmi Pg1XBOohG9Ogwjxpq1WQYpj4D2kZcgcuV495Mjz8VkwZ6EVNeprvmu42ZYWYBM20pzDO H+Sw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ffwll.ch header.s=google header.b=hody0FY6; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v16si4617867pgc.519.2019.01.31.07.00.27; Thu, 31 Jan 2019 07:00:43 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@ffwll.ch header.s=google header.b=hody0FY6; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731820AbfAaOq6 (ORCPT + 99 others); Thu, 31 Jan 2019 09:46:58 -0500 Received: from mail-ed1-f66.google.com ([209.85.208.66]:36127 "EHLO mail-ed1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726820AbfAaOq6 (ORCPT ); Thu, 31 Jan 2019 09:46:58 -0500 Received: by mail-ed1-f66.google.com with SMTP id f23so2805012edb.3 for ; Thu, 31 Jan 2019 06:46:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=kaGmse/o4tAPSO+AtMBVyQZx7oFQ4O6B+YYXQzR/2nU=; b=hody0FY6xDUmCyvX6sFfI7i0OwRS2bqkTNznMo6WUI43UQKeCjI7UyRQVPyFO07rT/ Zui1ReqyX8PvrFqIuUrwClHdaAwk6Yuef7msqX34sOYtuGxr7BqVFAQ9JwL5LTQ+VB0+ 8vpLKesLwSmUSrJTR7qU1Bu7yD1odAvliiZ74= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=kaGmse/o4tAPSO+AtMBVyQZx7oFQ4O6B+YYXQzR/2nU=; b=YXFV9Xk+ydLsowlP56nv4JD36r9CRmkef2zdqFk1fa+r7eTyLRwH64RPnLnMibk9Y3 tSWjune053qqopkcN1XXfhlZ4LQTBr36z18jeUzibvRoYdDFfPUSd1C/O2SFYHkrEH+t G0Cmre9w2qQlNCD6k7uu3CAKZmxssFUlyWOFlr0nu5JJrrBl+zCaPA9ozZvLJP6Ox1KC HfbeoJyWqqbT355f+pmlqp4ERgHNP6JnRg/7Gct25xg2NKVgu8iiUHbAlyaBCSFpdXn8 WPDwZdApqD5GKkkq5gRLNgsiTBONtC35gTNeLuNA++WMMmrocX9UTn5ndMfvlgegR4s9 c4XA== X-Gm-Message-State: AJcUukfPVU4xdlnHyMPCcE7iiIYCS4Y9B9xyD+CMiTA9YM40M4sL14le +quB44XHNkSrhoBjCkVgkX30wEOBIgNYaw== X-Received: by 2002:a17:906:5011:: with SMTP id s17mr16275624ejj.3.1548946014566; Thu, 31 Jan 2019 06:46:54 -0800 (PST) Received: from phenom.ffwll.local ([2a02:168:569e:0:3106:d637:d723:e855]) by smtp.gmail.com with ESMTPSA id g37sm1353680edb.85.2019.01.31.06.46.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 31 Jan 2019 06:46:53 -0800 (PST) From: Daniel Vetter To: DRI Development Cc: LKML , Daniel Vetter , "C, Ramalingam" , Greg Kroah-Hartman , Russell King , "Rafael J . Wysocki" , Jaroslav Kysela , Takashi Iwai , Rodrigo Vivi , Jani Nikula , Daniel Vetter Subject: [PATCH 1/2] component: Add documentation Date: Thu, 31 Jan 2019 15:46:39 +0100 Message-Id: <20190131144640.17896-1-daniel.vetter@ffwll.ch> X-Mailer: git-send-email 2.20.1 In-Reply-To: <1548917996-28081-2-git-send-email-ramalingam.c@intel.com> References: <1548917996-28081-2-git-send-email-ramalingam.c@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Someone owes me a beer ... While typing these I think doing an s/component_master/aggregate/ would be useful: - it's shorter :-) - I think component/aggregate is much more meaningful naming than component/puppetmaster or something like that. At least to my English ear "aggregate" emphasizes much more the "assemble a pile of things into something bigger" aspect, and there's not really much of a control hierarchy between aggregate and constituing components. But that's way more than a quick doc typing exercise ... Thanks to Ram for commenting on an initial draft of these docs. Cc: "C, Ramalingam" Cc: Greg Kroah-Hartman Cc: Russell King Cc: Rafael J. Wysocki Cc: Jaroslav Kysela Cc: Takashi Iwai Cc: Rodrigo Vivi Cc: Jani Nikula Signed-off-by: Daniel Vetter --- Documentation/driver-api/device_link.rst | 3 + Documentation/driver-api/index.rst | 1 + drivers/base/component.c | 107 ++++++++++++++++++++++- include/linux/component.h | 70 +++++++++++++++ 4 files changed, 178 insertions(+), 3 deletions(-) diff --git a/Documentation/driver-api/device_link.rst b/Documentation/driver-api/device_link.rst index d6763272e747..2d5919b2b337 100644 --- a/Documentation/driver-api/device_link.rst +++ b/Documentation/driver-api/device_link.rst @@ -1,6 +1,9 @@ .. |struct dev_pm_domain| replace:: :c:type:`struct dev_pm_domain ` .. |struct generic_pm_domain| replace:: :c:type:`struct generic_pm_domain ` + +.. _device_link: + ============ Device links ============ diff --git a/Documentation/driver-api/index.rst b/Documentation/driver-api/index.rst index ab38ced66a44..c0b600ed9961 100644 --- a/Documentation/driver-api/index.rst +++ b/Documentation/driver-api/index.rst @@ -22,6 +22,7 @@ available subsections can be seen below. device_connection dma-buf device_link + component message-based sound frame-buffer diff --git a/drivers/base/component.c b/drivers/base/component.c index ddcea8739c12..e5b04bce8544 100644 --- a/drivers/base/component.c +++ b/drivers/base/component.c @@ -16,6 +16,33 @@ #include #include +/** + * DOC: overview + * + * The component frameworks allows drivers to collect a pile of sub-devices, + * including their bound drivers, into an aggregate driver. Various subsystem + * already provide functions to get hold of such components, e.g. + * of_clk_get_by_name(). Anytime there's such a subsystem specific way to find a + * a device the component framework should not be used. The component framework + * fills the niche of aggregate drivers for specific hardware, where further + * standardization into a subsystem doesn't make sense. The common example is + * when a logical device (e.g. a DRM display driver) is spread around the SoC on + * various component (scanout engines, blending blocks, transcoders for various + * outputs and so on). + * + * The component framework also doesn't solve runtime dependencies, e.g. for + * system suspend and resume operations. See also :ref:`device + * links`. + * + * Components are registered using component_add() and unregistered with + * component_del(), usually from the driver's probe and disconnect functions. + * + * Aggregate drivers first assemble a component match list of what they need + * using component_match_add(). This is then registered as an aggregate driver + * using component_master_add_with_match(), and unregistered using + * component_master_del(). + */ + struct component; struct component_match_array { @@ -301,10 +328,24 @@ static int component_match_realloc(struct device *dev, return 0; } -/* - * Add a component to be matched, with a release function. +/** + * component_match_add_release - add a compent match with release callback + * @master: device with the aggregate driver + * @matchptr: pointer to the list of component matches + * @release: release function for @compare_data + * @compare: compare function to match against all components + * @compare_data: opaque pointer passed to the @compare function + * + * This adds a new component match to the list stored in @matchptr, which the + * @master aggregate driver needs to function. @matchptr must be initialized to + * NULL before adding the first match. + * + * The allocated match list in @matchptr is automatically released using devm + * actions. At that point @release will be called, to free any references held + * by @compare_data, e.g. when @compare_data is a &device_node that must be + * released with of_node_put(). * - * The match array is first created or extended if necessary. + * See also component_match_add(). */ void component_match_add_release(struct device *master, struct component_match **matchptr, @@ -367,6 +408,18 @@ static void free_master(struct master *master) kfree(master); } +/** + * component_master_add_with_match - register an aggregate driver + * @dev: device with the aggregate driver + * @ops: callbacks for the aggregate driver + * @match: component match list for the aggregate driver + * + * Registers a new aggregate driver consisting of the components added to @match + * by calling one of the component_match_add() functions. Once all components in + * @match are available it will be assembled by calling + * &component_master_ops.bind from @ops. Must be unregistered by calling + * component_master_del(). + */ int component_master_add_with_match(struct device *dev, const struct component_master_ops *ops, struct component_match *match) @@ -403,6 +456,15 @@ int component_master_add_with_match(struct device *dev, } EXPORT_SYMBOL_GPL(component_master_add_with_match); +/** + * component_master_del - unregister an aggregate driver + * @dev: device with the aggregate driver + * @ops: callbacks for the aggregate driver + * + * Unregistered an aggregate driver registered with + * component_master_add_with_match(). If necessary the aggregate driver is first + * disassembled by calling &component_master_ops.unbind from @ops. + */ void component_master_del(struct device *dev, const struct component_master_ops *ops) { @@ -430,6 +492,15 @@ static void component_unbind(struct component *component, devres_release_group(component->dev, component); } +/** + * component_unbind_all - unbind all component to an aggregate driver + * @master_dev: device with the aggregate driver + * @data: opaque pointer, passed to all components + * + * This unbinds all components to the aggregate @dev by passing @data to their + * &component_ops.unbind functions. Should be called from + * &component_master_ops.unbind. + */ void component_unbind_all(struct device *master_dev, void *data) { struct master *master; @@ -503,6 +574,15 @@ static int component_bind(struct component *component, struct master *master, return ret; } +/** + * component_bind_all - bind all component to an aggregate driver + * @master_dev: device with the aggregate driver + * @data: opaque pointer, passed to all components + * + * This binds all components to the aggregate @dev by passing @data to their + * &component_ops.bind functions. Should be called from + * &component_master_ops.bind. + */ int component_bind_all(struct device *master_dev, void *data) { struct master *master; @@ -537,6 +617,18 @@ int component_bind_all(struct device *master_dev, void *data) } EXPORT_SYMBOL_GPL(component_bind_all); +/** + * component_add - register a component + * @dev: component device + * @ops: component callbacks + * + * Register a new component for @dev. Functions in @ops will be call when the + * aggregate driver is ready to bind the overall driver by calling + * component_bind_all(). See also &struct component_ops. + * + * The component needs to be unregistered again at driver unload/disconnect by + * calling component_del(). + */ int component_add(struct device *dev, const struct component_ops *ops) { struct component *component; @@ -568,6 +660,15 @@ int component_add(struct device *dev, const struct component_ops *ops) } EXPORT_SYMBOL_GPL(component_add); +/** + * component_del - unregister a component + * @dev: component device + * @ops: component callbacks + * + * Unregister a component added with component_add(). If the component is bound + * into an aggregate driver this will force the entire aggrate driver, including + * all its components, to be unbound. + */ void component_del(struct device *dev, const struct component_ops *ops) { struct component *c, *component = NULL; diff --git a/include/linux/component.h b/include/linux/component.h index e71fbbbc74e2..67a899dd2e10 100644 --- a/include/linux/component.h +++ b/include/linux/component.h @@ -4,11 +4,31 @@ #include + struct device; +/** + * struct component_ops - callbacks for component drivers + * + * Components are registered with component_add() and unregistered with + * component_del(). + */ struct component_ops { + /** + * @bind: + * + * Called through component_bind_all() when the aggregate driver is + * ready to bind the overall driver. + */ int (*bind)(struct device *comp, struct device *master, void *master_data); + /** + * @unbind: + * + * Called through component_unbind_all() when the aggregate driver is + * ready to bind the overall driver, or when component_bind_all() fails + * part-ways through and needs to unbind some already bound components. + */ void (*unbind)(struct device *comp, struct device *master, void *master_data); }; @@ -21,8 +41,42 @@ void component_unbind_all(struct device *master, void *master_data); struct master; +/** + * struct component_master_ops - callback for the aggregate driver + * + * Aggregate drivers are registered with component_master_add_with_match() and + * unregistered with component_master_del(). + */ struct component_master_ops { + /** + * @bind: + * + * Called when all components or the aggregate driver, as specified in + * the match list passed to component_master_add_with_match(), are + * ready. Usually there are 3 steps to bind an aggregate driver: + * + * 1. Allocate a structure for the aggregate driver. + * + * 2. Bind all components to the aggregate driver by calling + * component_bind_all() with the aggregate driver structure as opaque + * pointer data. + * + * 3. Register the aggregate driver with the subsystem to publish its + * interfaces. + * + * Note that the lifetime of the aggregate driver does not align with + * any of the underlying &struct device instances. Therefore devm cannot + * be used and all resources acquired or allocated in this callback must + * be expecitly released in the @unbind callback. + */ int (*bind)(struct device *master); + /** + * @unbind: + * + * Called when either the aggregate driver, using + * component_master_del(), or one of its components, using + * component_del(), is unregistered. + */ void (*unbind)(struct device *master); }; @@ -38,6 +92,22 @@ void component_match_add_release(struct device *master, void (*release)(struct device *, void *), int (*compare)(struct device *, void *), void *compare_data); +/** + * component_match_add - add a compent match + * @master: device with the aggregate driver + * @matchptr: pointer to the list of component matches + * @compare: compare function to match against all components + * @compare_data: opaque pointer passed to the @compare function + * + * This adds a new component match to the list stored in @matchptr, which the + * @master aggregate driver needs to function. @matchptr must be initialized to + * NULL before adding the first match. + * + * The allocated match list in @matchptr is automatically released using devm + * actions. + * + * See also component_match_add_release(). + */ static inline void component_match_add(struct device *master, struct component_match **matchptr, int (*compare)(struct device *, void *), void *compare_data) -- 2.20.1