From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Christopher Heiny <cheiny@synaptics.com>
Cc: Linux Input <linux-input@vger.kernel.org>,
Andrew Duggan <aduggan@synaptics.com>,
Vincent Huang <vincent.huang@tw.synaptics.com>,
Vivian Ly <vly@synaptics.com>,
Daniel Rosenberg <daniel.rosenberg@synaptics.com>,
Jean Delvare <khali@linux-fr.org>,
Joerie de Gram <j.de.gram@gmail.com>,
Linus Walleij <linus.walleij@stericsson.com>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>
Subject: Re: [PATCH] input synaptics-rmi4: move rmi_f01 query register parsing to its own function
Date: Thu, 9 Jan 2014 00:18:23 -0800 [thread overview]
Message-ID: <20140109081823.GD27160@core.coreip.homeip.net> (raw)
In-Reply-To: <1389142930-26279-1-git-send-email-cheiny@synaptics.com>
On Tue, Jan 07, 2014 at 05:02:10PM -0800, Christopher Heiny wrote:
> In the near future, query register parsing is going to get a lot more
> complicated. It's also going to be needed by the reflash code. Now is the
> time to move this from the F01 initialization into its own function,
> while the code is still fairly simple.
>
> Signed-off-by: Christopher Heiny <cheiny@synaptics.com>
> Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>
>
Applied, thank you.
> ---
>
> drivers/input/rmi4/rmi_f01.c | 71 +++++++++++++++++++++++++++-----------------
> 1 file changed, 43 insertions(+), 28 deletions(-)
>
> diff --git a/drivers/input/rmi4/rmi_f01.c b/drivers/input/rmi4/rmi_f01.c
> index d547633..1cb11ea 100644
> --- a/drivers/input/rmi4/rmi_f01.c
> +++ b/drivers/input/rmi4/rmi_f01.c
> @@ -167,6 +167,46 @@ static int rmi_f01_alloc_memory(struct rmi_function *fn,
> return 0;
> }
>
> +static int rmi_f01_read_properties(struct rmi_device *rmi_dev,
> + u16 query_base_addr,
> + struct f01_basic_properties *props)
> +{
> + u8 basic_query[RMI_F01_BASIC_QUERY_LEN];
> + int error;
> +
> + error = rmi_read_block(rmi_dev, query_base_addr,
> + basic_query, sizeof(basic_query));
> + if (error < 0) {
> + dev_err(&rmi_dev->dev, "Failed to read device query registers.\n");
> + return error;
> + }
> +
> + /* Now parse what we got */
> + props->manufacturer_id = basic_query[0];
> +
> + props->has_lts = basic_query[1] & RMI_F01_QRY1_HAS_LTS;
> + props->has_adjustable_doze =
> + basic_query[1] & RMI_F01_QRY1_HAS_ADJ_DOZE;
> + props->has_adjustable_doze_holdoff =
> + basic_query[1] & RMI_F01_QRY1_HAS_ADJ_DOZE_HOFF;
> +
> + snprintf(props->dom, sizeof(props->dom),
> + "20%02x%02x%02x",
> + basic_query[5] & RMI_F01_QRY5_YEAR_MASK,
> + basic_query[6] & RMI_F01_QRY6_MONTH_MASK,
> + basic_query[7] & RMI_F01_QRY7_DAY_MASK);
> +
> + memcpy(props->product_id, &basic_query[11],
> + RMI_PRODUCT_ID_LENGTH);
> + props->product_id[RMI_PRODUCT_ID_LENGTH] = '\0';
> +
> + props->productinfo =
> + ((basic_query[2] & RMI_F01_QRY2_PRODINFO_MASK) << 7) |
> + (basic_query[3] & RMI_F01_QRY2_PRODINFO_MASK);
> +
> + return 0;
> +}
> +
> static int rmi_f01_initialize(struct rmi_function *fn)
> {
> u8 temp;
> @@ -176,7 +216,6 @@ static int rmi_f01_initialize(struct rmi_function *fn)
> struct rmi_driver_data *driver_data = dev_get_drvdata(&rmi_dev->dev);
> struct f01_data *data = fn->data;
> struct rmi_device_platform_data *pdata = to_rmi_platform_data(rmi_dev);
> - u8 basic_query[RMI_F01_BASIC_QUERY_LEN];
>
> mutex_init(&data->control_mutex);
>
> @@ -248,36 +287,12 @@ static int rmi_f01_initialize(struct rmi_function *fn)
> return error;
> }
>
> - error = rmi_read_block(rmi_dev, fn->fd.query_base_addr,
> - basic_query, sizeof(basic_query));
> + error = rmi_f01_read_properties(rmi_dev, fn->fd.query_base_addr,
> + &data->properties);
> if (error < 0) {
> - dev_err(&fn->dev, "Failed to read device query registers.\n");
> + dev_err(&fn->dev, "Failed to read F01 properties.\n");
> return error;
> }
> -
> - /* Now parse what we got */
> - data->properties.manufacturer_id = basic_query[0];
> -
> - data->properties.has_lts = basic_query[1] & RMI_F01_QRY1_HAS_LTS;
> - data->properties.has_adjustable_doze =
> - basic_query[1] & RMI_F01_QRY1_HAS_ADJ_DOZE;
> - data->properties.has_adjustable_doze_holdoff =
> - basic_query[1] & RMI_F01_QRY1_HAS_ADJ_DOZE_HOFF;
> -
> - snprintf(data->properties.dom, sizeof(data->properties.dom),
> - "20%02x%02x%02x",
> - basic_query[5] & RMI_F01_QRY5_YEAR_MASK,
> - basic_query[6] & RMI_F01_QRY6_MONTH_MASK,
> - basic_query[7] & RMI_F01_QRY7_DAY_MASK);
> -
> - memcpy(data->properties.product_id, &basic_query[11],
> - RMI_PRODUCT_ID_LENGTH);
> - data->properties.product_id[RMI_PRODUCT_ID_LENGTH] = '\0';
> -
> - data->properties.productinfo =
> - ((basic_query[2] & RMI_F01_QRY2_PRODINFO_MASK) << 7) |
> - (basic_query[3] & RMI_F01_QRY2_PRODINFO_MASK);
> -
> dev_info(&fn->dev, "found RMI device, manufacturer: %s, product: %s\n",
> data->properties.manufacturer_id == 1 ?
> "Synaptics" : "unknown",
--
Dmitry
prev parent reply other threads:[~2014-01-09 8:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 1:02 [PATCH] input synaptics-rmi4: move rmi_f01 query register parsing to its own function Christopher Heiny
2014-01-09 8:18 ` Dmitry Torokhov [this message]
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=20140109081823.GD27160@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=aduggan@synaptics.com \
--cc=benjamin.tissoires@redhat.com \
--cc=cheiny@synaptics.com \
--cc=daniel.rosenberg@synaptics.com \
--cc=j.de.gram@gmail.com \
--cc=khali@linux-fr.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-input@vger.kernel.org \
--cc=vincent.huang@tw.synaptics.com \
--cc=vly@synaptics.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).