X86 platform drivers
 help / color / mirror / Atom feed
From: <michaelsh@nvidia.com>
To: <hdegoede@redhat.com>
Cc: <platform-driver-x86@vger.kernel.org>, <vadimp@nvidia.com>,
	Michael Shych <michaelsh@nvidia.com>
Subject: [PATCH v1 1/3] platform_data/mlxreg: Add field for notification callback
Date: Sat, 30 Apr 2022 14:58:07 +0300	[thread overview]
Message-ID: <20220430115809.54565-2-michaelsh@nvidia.com> (raw)
In-Reply-To: <20220430115809.54565-1-michaelsh@nvidia.com>

From: Michael Shych <michaelsh@nvidia.com>

Add notification callback to inform caller that platform driver probing
has been completed. It allows to caller to perform some initialization
flow steps depending on specific driver probing completion.

Signed-off-by: Michael Shych <michaelsh@nvidia.com>
Reviewed-by: Vadim Pasternak <vadimp@nvidia.com>
---
 include/linux/platform_data/mlxreg.h | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/include/linux/platform_data/mlxreg.h b/include/linux/platform_data/mlxreg.h
index 40185f9d7c14..a6bd74e29b6b 100644
--- a/include/linux/platform_data/mlxreg.h
+++ b/include/linux/platform_data/mlxreg.h
@@ -216,6 +216,8 @@ struct mlxreg_core_platform_data {
  * @mask_low: low aggregation interrupt common mask;
  * @deferred_nr: I2C adapter number must be exist prior probing execution;
  * @shift_nr: I2C adapter numbers must be incremented by this value;
+ * @handle: handle to be passed by callback;
+ * @completion_notify: callback to notify when platform driver probing is done;
  */
 struct mlxreg_core_hotplug_platform_data {
 	struct mlxreg_core_item *items;
@@ -228,6 +230,8 @@ struct mlxreg_core_hotplug_platform_data {
 	u32 mask_low;
 	int deferred_nr;
 	int shift_nr;
+	void *handle;
+	int (*completion_notify)(void *handle, int id);
 };
 
 #endif /* __LINUX_PLATFORM_DATA_MLXREG_H */
-- 
2.14.1


  reply	other threads:[~2022-04-30 11:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-30 11:58 [PATCH v1 0/3] Add support for new SN2201 system michaelsh
2022-04-30 11:58 ` michaelsh [this message]
2022-05-11 14:34   ` [PATCH v1 1/3] platform_data/mlxreg: Add field for notification callback Hans de Goede
2022-04-30 11:58 ` [PATCH v1 2/3] platform/mellanox: Add support for new SN2201 system michaelsh
2022-05-11 14:35   ` Hans de Goede
2022-04-30 11:58 ` [PATCH v1 3/3] Documentation/ABI: Add new attributes for mlxreg-io sysfs interfaces michaelsh
2022-05-11 14:40   ` Hans de Goede
2022-05-11 14:58     ` Michael Shych
2022-05-11 15:15       ` Hans de Goede
2022-05-11 15:35         ` Michael Shych

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=20220430115809.54565-2-michaelsh@nvidia.com \
    --to=michaelsh@nvidia.com \
    --cc=hdegoede@redhat.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=vadimp@nvidia.com \
    /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