linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Jacek Anaszewski <jacek.anaszewski@gmail.com>,
	Pavel Machek <pavel@ucw.cz>, Lee Jones <lee.jones@linaro.org>,
	Sebastian Reichel <sre@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
	devicetree@vger.kernel.org, linux-input@vger.kernel.org,
	linux-leds@vger.kernel.org, linux-pm@vger.kernel.org,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: [PATCH v8 05/11] mfd: core: document mfd_add_devices()
Date: Wed,  3 Apr 2019 11:01:02 +0200	[thread overview]
Message-ID: <20190403090108.24788-6-brgl@bgdev.pl> (raw)
In-Reply-To: <20190403090108.24788-1-brgl@bgdev.pl>

From: Bartosz Golaszewski <bgolaszewski@baylibre.com>

Add a kernel doc for mfd_add_devices().

Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Acked-by: Pavel Machek <pavel@ucw.cz>
---
 drivers/mfd/mfd-core.c | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/drivers/mfd/mfd-core.c b/drivers/mfd/mfd-core.c
index 94e3f32ce935..1ade4c8cc91f 100644
--- a/drivers/mfd/mfd-core.c
+++ b/drivers/mfd/mfd-core.c
@@ -269,6 +269,19 @@ static int mfd_add_device(struct device *parent, int id,
 	return ret;
 }
 
+/**
+ * mfd_add_devices - register child devices
+ *
+ * @parent:	Pointer to parent device.
+ * @id:		Can be PLATFORM_DEVID_AUTO to let the Platform API take care
+ *		of device numbering, or will be added to a device's cell_id.
+ * @cells:	Array of (struct mfd_cell)s describing child devices.
+ * @n_devs:	Number of child devices to register.
+ * @mem_base:	Parent register range resource for child devices.
+ * @irq_base:	Base of the range of virtual interrupt numbers allocated for
+ *		this MFD device. Unused if @domain is specified.
+ * @domain:	Interrupt domain to create mappings for hardware interrupts.
+ */
 int mfd_add_devices(struct device *parent, int id,
 		    const struct mfd_cell *cells, int n_devs,
 		    struct resource *mem_base,
-- 
2.21.0


  parent reply	other threads:[~2019-04-03  9:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-03  9:00 [PATCH v8 00/11] mfd: add support for max77650 PMIC Bartosz Golaszewski
2019-04-03  9:00 ` [PATCH v8 01/11] dt-bindings: mfd: add DT bindings for max77650 Bartosz Golaszewski
2019-04-03  9:00 ` [PATCH v8 02/11] dt-bindings: power: supply: " Bartosz Golaszewski
2019-04-06  7:07   ` Rob Herring
2019-04-08 12:25     ` Bartosz Golaszewski
2019-04-09  1:10       ` Rob Herring
2019-04-09 11:04         ` Bartosz Golaszewski
2019-04-09 15:38           ` Bartosz Golaszewski
2019-04-11 16:50             ` Rob Herring
2019-04-03  9:01 ` [PATCH v8 03/11] dt-bindings: leds: " Bartosz Golaszewski
2019-04-04 13:22   ` Pavel Machek
2019-04-03  9:01 ` [PATCH v8 04/11] dt-bindings: input: " Bartosz Golaszewski
2019-04-03  9:01 ` Bartosz Golaszewski [this message]
2019-04-04  7:04   ` [PATCH v8 05/11] mfd: core: document mfd_add_devices() Lee Jones
2019-04-03  9:01 ` [PATCH v8 06/11] mfd: max77650: new core mfd driver Bartosz Golaszewski
2019-04-04  7:15   ` Lee Jones
2019-04-04  7:30     ` Bartosz Golaszewski
2019-04-03  9:01 ` [PATCH v8 07/11] power: supply: max77650: add support for battery charger Bartosz Golaszewski
2019-04-03  9:01 ` [PATCH v8 08/11] gpio: max77650: add GPIO support Bartosz Golaszewski
2019-04-03  9:01 ` [PATCH v8 09/11] leds: max77650: add LEDs support Bartosz Golaszewski
2019-04-04 13:22   ` Pavel Machek
2019-04-03  9:01 ` [PATCH v8 10/11] input: max77650: add onkey support Bartosz Golaszewski
2019-04-03  9:01 ` [PATCH v8 11/11] MAINTAINERS: add an entry for max77650 mfd driver Bartosz Golaszewski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190403090108.24788-6-brgl@bgdev.pl \
    --to=brgl@bgdev.pl \
    --cc=bgolaszewski@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jacek.anaszewski@gmail.com \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pavel@ucw.cz \
    --cc=robh+dt@kernel.org \
    --cc=sre@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).