From: Sakari Ailus <sakari.ailus@iki.fi>
To: linux-media@vger.kernel.org
Cc: linux-leds@vger.kernel.org, j.anaszewski@samsung.com,
cooloney@gmail.com, g.liakhovetski@gmx.de,
s.nawrocki@samsung.com, laurent.pinchart@ideasonboard.com,
mchehab@osg.samsung.com
Subject: [PATCH 3/5] v4l: flash: Pass struct device and device_node to v4l2_flash_init()
Date: Wed, 20 May 2015 02:04:03 +0300 [thread overview]
Message-ID: <1432076645-4799-4-git-send-email-sakari.ailus@iki.fi> (raw)
In-Reply-To: <1432076645-4799-1-git-send-email-sakari.ailus@iki.fi>
The V4L2 sub-device node's dev will thus refer to the physical device, not
the LED flash device node. Also matching against device_node is possible in
cases where the LED flash controller drives multiple LEDs.
Signed-off-by: Sakari Ailus <sakari.ailus@iki.fi>
---
drivers/media/v4l2-core/v4l2-flash.c | 10 ++++++----
include/media/v4l2-flash.h | 10 +++++++---
2 files changed, 13 insertions(+), 7 deletions(-)
diff --git a/drivers/media/v4l2-core/v4l2-flash.c b/drivers/media/v4l2-core/v4l2-flash.c
index bed2036..d182adc 100644
--- a/drivers/media/v4l2-core/v4l2-flash.c
+++ b/drivers/media/v4l2-core/v4l2-flash.c
@@ -542,9 +542,10 @@ static const struct v4l2_subdev_ops v4l2_flash_subdev_ops = {
.core = &v4l2_flash_core_ops,
};
-struct v4l2_flash *v4l2_flash_init(struct led_classdev_flash *fled_cdev,
- const struct v4l2_flash_ops *ops,
- struct v4l2_flash_config *config)
+struct v4l2_flash *v4l2_flash_init(
+ struct device *dev, struct device_node *of_node,
+ struct led_classdev_flash *fled_cdev, const struct v4l2_flash_ops *ops,
+ struct v4l2_flash_config *config)
{
struct v4l2_flash *v4l2_flash;
struct led_classdev *led_cdev = &fled_cdev->led_cdev;
@@ -562,7 +563,8 @@ struct v4l2_flash *v4l2_flash_init(struct led_classdev_flash *fled_cdev,
sd = &v4l2_flash->sd;
v4l2_flash->fled_cdev = fled_cdev;
v4l2_flash->ops = ops;
- sd->dev = led_cdev->dev;
+ sd->dev = dev;
+ sd->of_node = of_node;
v4l2_subdev_init(sd, &v4l2_flash_subdev_ops);
sd->internal_ops = &v4l2_flash_subdev_internal_ops;
sd->flags |= V4L2_SUBDEV_FL_HAS_DEVNODE;
diff --git a/include/media/v4l2-flash.h b/include/media/v4l2-flash.h
index 67a2cbf..31e421d 100644
--- a/include/media/v4l2-flash.h
+++ b/include/media/v4l2-flash.h
@@ -115,6 +115,8 @@ static inline struct v4l2_flash *v4l2_ctrl_to_v4l2_flash(struct v4l2_ctrl *c)
#if IS_ENABLED(CONFIG_V4L2_FLASH_LED_CLASS)
/**
* v4l2_flash_init - initialize V4L2 flash led sub-device
+ * @dev: flash device, e.g. an I2C device
+ * @of_node: of_node of the LED, may be NULL if the same as device's
* @fled_cdev: the LED Flash class device to wrap
* @flash_ops: V4L2 Flash device ops
* @config: initialization data for V4L2 Flash sub-device
@@ -125,9 +127,10 @@ static inline struct v4l2_flash *v4l2_ctrl_to_v4l2_flash(struct v4l2_ctrl *c)
* value is encoded using ERR_PTR(). Use IS_ERR() to check and
* PTR_ERR() to obtain the numeric return value.
*/
-struct v4l2_flash *v4l2_flash_init(struct led_classdev_flash *fled_cdev,
- const struct v4l2_flash_ops *ops,
- struct v4l2_flash_config *config);
+struct v4l2_flash *v4l2_flash_init(
+ struct device *dev, struct device_node *of_node,
+ struct led_classdev_flash *fled_cdev, const struct v4l2_flash_ops *ops,
+ struct v4l2_flash_config *config);
/**
* v4l2_flash_release - release V4L2 Flash sub-device
@@ -139,6 +142,7 @@ void v4l2_flash_release(struct v4l2_flash *v4l2_flash);
#else
static inline struct v4l2_flash *v4l2_flash_init(
+ struct device *dev, struct device_node *of_node,
struct led_classdev_flash *fled_cdev, const struct v4l2_flash_ops *ops,
struct v4l2_flash_config *config)
{
--
1.7.10.4
next prev parent reply other threads:[~2015-05-19 23:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 23:04 [PATCH 0/5] V4L2 flash API wrapper improvements Sakari Ailus
2015-05-19 23:04 ` [PATCH 1/5] v4l: async: Add a pointer to of_node to struct v4l2_subdev, match it Sakari Ailus
2015-05-20 14:20 ` Jacek Anaszewski
2015-05-23 18:47 ` Laurent Pinchart
2015-05-31 21:54 ` Sakari Ailus
2015-05-31 22:24 ` [PATCH v1.1 " Sakari Ailus
2015-06-02 2:47 ` Laurent Pinchart
2015-06-09 8:05 ` Sakari Ailus
2015-06-10 21:27 ` [PATCH v1.2 " Sakari Ailus
2015-06-11 19:18 ` [PATCH v1.3 " Sakari Ailus
2015-06-11 19:27 ` Laurent Pinchart
2015-06-12 6:41 ` Sakari Ailus
2015-06-15 18:34 ` Bryan Wu
2015-05-19 23:04 ` [PATCH 2/5] v4l: flash: Make v4l2_flash_init() and v4l2_flash_release() functions always Sakari Ailus
2015-05-23 18:40 ` Laurent Pinchart
2015-05-19 23:04 ` Sakari Ailus [this message]
2015-05-19 23:04 ` [PATCH 4/5] leds: aat1290: Pass dev and dev->of_node to v4l2_flash_init() Sakari Ailus
2015-05-20 9:47 ` Jacek Anaszewski
2015-05-20 10:19 ` Sakari Ailus
2015-05-20 10:37 ` Jacek Anaszewski
2015-05-20 12:27 ` Sakari Ailus
2015-05-20 13:47 ` Jacek Anaszewski
2015-05-20 14:31 ` Sakari Ailus
2015-05-21 8:54 ` Jacek Anaszewski
2015-05-21 10:06 ` Sakari Ailus
2015-05-21 12:13 ` Jacek Anaszewski
2015-05-21 13:14 ` Sakari Ailus
2015-05-19 23:04 ` [PATCH 5/5] leds: max77693: " Sakari Ailus
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=1432076645-4799-4-git-send-email-sakari.ailus@iki.fi \
--to=sakari.ailus@iki.fi \
--cc=cooloney@gmail.com \
--cc=g.liakhovetski@gmx.de \
--cc=j.anaszewski@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-leds@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=s.nawrocki@samsung.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;
as well as URLs for NNTP newsgroup(s).