public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Dyer <nick@shmanahar.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-media@vger.kernel.org,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	Benson Leung <bleung@chromium.org>,
	Alan Bowens <Alan.Bowens@atmel.com>,
	Javier Martinez Canillas <javier@osg.samsung.com>,
	Chris Healy <cphealy@gmail.com>,
	Henrik Rydberg <rydberg@bitmath.org>,
	Andrew Duggan <aduggan@synaptics.com>,
	James Chen <james.chen@emc.com.tw>, Dudley Du <dudl@cypress.com>,
	Andrew de los Reyes <adlr@chromium.org>,
	sheckylin@chromium.org, Peter Hutterer <peter.hutterer@who-t.net>,
	Florian Echtler <floe@butterbrot.org>,
	mchehab@osg.samsung.com, jon.older@itdev.co.uk,
	nick.dyer@itdev.co.uk
Subject: Re: [PATCH v6 10/11] Input: synaptics-rmi4 - add support for F54 diagnostics
Date: Fri, 1 Jul 2016 09:41:24 +0100	[thread overview]
Message-ID: <20160701084124.GA6384@bm.shmanahar.org> (raw)
In-Reply-To: <1467308334-12580-11-git-send-email-nick@shmanahar.org>

On Thu, Jun 30, 2016 at 06:38:53PM +0100, Nick Dyer wrote:
> Function 54 implements access to various RMI4 diagnostic features.
> 
> This patch adds support for retrieving this data. It registers a V4L2
> device to output the data to user space.
> 
> Signed-off-by: Nick Dyer <nick@shmanahar.org>
> ---
>  drivers/input/rmi4/Kconfig      |  11 +
>  drivers/input/rmi4/Makefile     |   1 +
>  drivers/input/rmi4/rmi_bus.c    |   3 +
>  drivers/input/rmi4/rmi_driver.h |   1 +
>  drivers/input/rmi4/rmi_f54.c    | 754 ++++++++++++++++++++++++++++++++++++++++
>  5 files changed, 770 insertions(+)
>  create mode 100644 drivers/input/rmi4/rmi_f54.c
[...]
> index 0000000..2361157
> --- /dev/null
> +++ b/drivers/input/rmi4/rmi_f54.c
[...]
> +static int rmi_f54_vidioc_querycap(struct file *file, void *priv,
> +				   struct v4l2_capability *cap)
> +{
> +	struct f54_data *f54 = video_drvdata(file);
> +
> +	strlcpy(cap->driver, F54_NAME, sizeof(cap->driver));
> +	strlcpy(cap->card, SYNAPTICS_INPUT_DEVICE_NAME, sizeof(cap->card));
> +	strlcpy(cap->bus_info, dev_name(&f54->fn->dev), sizeof(cap->bus_info));

I need to correct this to prefix the bus. RMI4 registers its own bus, so
devices appear under eg /sys/bus/rmi4/devices/rmi4-00.fn54

So I will change to:
snprintf(cap->bus_info, sizeof(cap->bus_info), "rmi4:%s", dev_name(&f54->fn->dev));

And I will need to add rmi4 to the valid prefixes in v4l2-complaince as well.

> +
> +	return 0;
> +}

  reply	other threads:[~2016-07-01  8:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-30 17:38 [PATCH v6 0/11] Output raw touch data via V4L2 Nick Dyer
2016-06-30 17:38 ` [PATCH v6 01/11] Input: atmel_mxt_ts - update MAINTAINERS email address Nick Dyer
2016-06-30 17:38 ` [PATCH v6 02/11] [media] v4l2-core: Add support for touch devices Nick Dyer
2016-06-30 17:38 ` [PATCH v6 03/11] [media] DocBook: add " Nick Dyer
2016-06-30 17:38 ` [PATCH v6 04/11] Input: atmel_mxt_ts - add support for T37 diagnostic data Nick Dyer
2016-06-30 17:38 ` [PATCH v6 05/11] Input: atmel_mxt_ts - output diagnostic debug via V4L2 device Nick Dyer
2016-06-30 17:38 ` [PATCH v6 06/11] Input: atmel_mxt_ts - read touchscreen size Nick Dyer
2016-06-30 17:38 ` [PATCH v6 07/11] Input: atmel_mxt_ts - handle diagnostic data orientation Nick Dyer
2016-06-30 17:38 ` [PATCH v6 08/11] Input: atmel_mxt_ts - add diagnostic data support for mXT1386 Nick Dyer
2016-06-30 17:38 ` [PATCH v6 09/11] Input: atmel_mxt_ts - add support for reference data Nick Dyer
2016-06-30 17:38 ` [PATCH v6 10/11] Input: synaptics-rmi4 - add support for F54 diagnostics Nick Dyer
2016-07-01  8:41   ` Nick Dyer [this message]
2016-07-01 19:16   ` Andrew Duggan
2016-06-30 17:38 ` [PATCH v6 11/11] Input: sur40 - use new V4L2 touch input type Nick Dyer
2016-07-03 18:11   ` Florian Echtler
2016-08-05 13:39   ` Pavel Machek
2016-06-30 17:42 ` [PATCH] v4l2-compliance: Changes to support touch sensors Nick Dyer

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=20160701084124.GA6384@bm.shmanahar.org \
    --to=nick@shmanahar.org \
    --cc=Alan.Bowens@atmel.com \
    --cc=adlr@chromium.org \
    --cc=aduggan@synaptics.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=bleung@chromium.org \
    --cc=cphealy@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=dudl@cypress.com \
    --cc=floe@butterbrot.org \
    --cc=hverkuil@xs4all.nl \
    --cc=james.chen@emc.com.tw \
    --cc=javier@osg.samsung.com \
    --cc=jon.older@itdev.co.uk \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@osg.samsung.com \
    --cc=nick.dyer@itdev.co.uk \
    --cc=peter.hutterer@who-t.net \
    --cc=rydberg@bitmath.org \
    --cc=sheckylin@chromium.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