From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mark Brown <broonie@kernel.org>,
Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Bartosz Golaszewski <brgl@kernel.org>,
linux-kernel@vger.kernel.org, driver-core@lists.linux.dev,
linux-gpio@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
Linus Walleij <linusw@kernel.org>,
Michael Walle <mwalle@kernel.org>,
Yu-Chun Lin <eleanor.lin@realtek.com>,
William Breathitt Gray <wbg@kernel.org>
Subject: [PATCH v1 4/4] gpio: regmap: Order kernel-doc descriptions with the actual appearance
Date: Thu, 2 Jul 2026 14:42:57 +0200 [thread overview]
Message-ID: <20260702130903.1790633-5-andriy.shevchenko@linux.intel.com> (raw)
In-Reply-To: <20260702130903.1790633-1-andriy.shevchenko@linux.intel.com>
Order kernel-doc descriptions with the actual appearance.
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
include/linux/gpio/regmap.h | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/include/linux/gpio/regmap.h b/include/linux/gpio/regmap.h
index e939709fde8d..a3ba8242c353 100644
--- a/include/linux/gpio/regmap.h
+++ b/include/linux/gpio/regmap.h
@@ -34,10 +34,6 @@ struct regmap;
* @ngpio_per_reg: (Optional) Number of GPIOs per register
* @irq_domain: (Optional) IRQ domain if the controller is
* interrupt-capable
- * @reg_mask_xlate: (Optional) Translates base address and GPIO
- * offset to a register/bitmask pair. If not
- * given the default gpio_regmap_simple_xlate()
- * is used.
* @fixed_direction_mask:
* (Optional) Bitmap representing the GPIO lines that
* make use of the @fixed_direction_output list to
@@ -48,16 +44,20 @@ struct regmap;
* (Optional) Bitmap representing the fixed direction of
* the GPIO lines. Useful when there are GPIO lines with a
* fixed direction mixed together in the same register.
- * @drvdata: (Optional) Pointer to driver specific data which is
- * not used by gpio-remap but is provided "as is" to the
- * driver callback(s).
- * @init_valid_mask: (Optional) Routine to initialize @valid_mask, to be used
- * if not all GPIOs are valid.
* @regmap_irq_chip: (Optional) Pointer on an regmap_irq_chip structure. If
* set, a regmap-irq device will be created and the IRQ
* domain will be set accordingly.
* @regmap_irq_line: (Optional) The IRQ the device uses to signal interrupts.
* @regmap_irq_flags: (Optional) The IRQF_ flags to use for the interrupt.
+ * @reg_mask_xlate: (Optional) Translates base address and GPIO
+ * offset to a register/bitmask pair. If not
+ * given the default gpio_regmap_simple_xlate()
+ * is used.
+ * @init_valid_mask: (Optional) Routine to initialize @valid_mask, to be used
+ * if not all GPIOs are valid.
+ * @drvdata: (Optional) Pointer to driver specific data which is
+ * not used by gpio-remap but is provided "as is" to the
+ * driver callback(s).
*
* The ->reg_mask_xlate translates a given base address and GPIO offset to
* register and mask pair. The base address is one of the given register
--
2.50.1
next prev parent reply other threads:[~2026-07-02 13:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 12:42 [PATCH v1 0/4] gpio: regmap: Keep tracking IRQ requests and releases Andy Shevchenko
2026-07-02 12:42 ` [PATCH v1 1/4] regmap-irq: Provide IRQ resource request and release callbacks Andy Shevchenko
2026-07-03 15:29 ` Mark Brown
2026-07-02 12:42 ` [PATCH v1 2/4] gpio: regmap: Provide default " Andy Shevchenko
2026-07-03 11:29 ` Andy Shevchenko
2026-07-02 12:42 ` [PATCH v1 3/4] gpio: regmap: Apply default resource callbacks for regmap IRQ chip Andy Shevchenko
2026-07-03 20:52 ` Linus Walleij
2026-07-02 12:42 ` Andy Shevchenko [this message]
2026-07-03 20:51 ` [PATCH v1 4/4] gpio: regmap: Order kernel-doc descriptions with the actual appearance Linus Walleij
2026-07-03 8:17 ` [PATCH v1 0/4] gpio: regmap: Keep tracking IRQ requests and releases Yu-Chun Lin [林祐君]
2026-07-03 8:34 ` Bartosz Golaszewski
2026-07-03 15:29 ` (subset) " Mark Brown
2026-07-04 5:21 ` William Breathitt Gray
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=20260702130903.1790633-5-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=brgl@kernel.org \
--cc=broonie@kernel.org \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=eleanor.lin@realtek.com \
--cc=gregkh@linuxfoundation.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=mwalle@kernel.org \
--cc=rafael@kernel.org \
--cc=wbg@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