linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christopher Heiny <cheiny@synaptics.com>
To: Courtney Cavin <courtney.cavin@sonymobile.com>,
	linux-input@vger.kernel.org
Cc: dmitry.torokhov@gmail.com
Subject: Re: [PATCH 04/15] Input: synaptics-rmi4 - remove sensor name from platform data
Date: Tue, 4 Feb 2014 15:08:29 -0800	[thread overview]
Message-ID: <52F172ED.1040902@synaptics.com> (raw)
In-Reply-To: <1390521623-6491-5-git-send-email-courtney.cavin@sonymobile.com>

On 01/23/2014 04:00 PM, Courtney Cavin wrote:
> The driver/device already has a name, no need for another one.

This is extremely useful in initial system bring up on systems with more 
than one RMI4 sensor.  We'd prefer to keep this.

>
> Cc: Christopher Heiny <cheiny@synaptics.com>
> Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> Signed-off-by: Courtney Cavin <courtney.cavin@sonymobile.com>
> ---
>   drivers/input/rmi4/rmi_bus.c    | 4 ++--
>   drivers/input/rmi4/rmi_driver.c | 7 ++-----
>   drivers/input/rmi4/rmi_f11.c    | 3 +--
>   drivers/input/rmi4/rmi_i2c.c    | 3 +--
>   include/linux/rmi.h             | 4 ----
>   5 files changed, 6 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/input/rmi4/rmi_bus.c b/drivers/input/rmi4/rmi_bus.c
> index cd7bfbd..fd14acb 100644
> --- a/drivers/input/rmi4/rmi_bus.c
> +++ b/drivers/input/rmi4/rmi_bus.c
> @@ -116,8 +116,8 @@ int rmi_register_transport_device(struct rmi_transport_dev *xport)
>   		return error;
>   	}
>
> -	dev_dbg(xport->dev, "%s: Registered %s as %s.\n", __func__,
> -		pdata->sensor_name, dev_name(&rmi_dev->dev));
> +	dev_dbg(xport->dev, "%s: Registered %s\n", __func__,
> +		dev_name(&rmi_dev->dev));
>
>   	return 0;
>   }
> diff --git a/drivers/input/rmi4/rmi_driver.c b/drivers/input/rmi4/rmi_driver.c
> index 4965589..5fb582c 100644
> --- a/drivers/input/rmi4/rmi_driver.c
> +++ b/drivers/input/rmi4/rmi_driver.c
> @@ -531,12 +531,10 @@ static int create_function(struct rmi_device *rmi_dev,
>   {
>   	struct device *dev = &rmi_dev->dev;
>   	struct rmi_driver_data *data = dev_get_drvdata(&rmi_dev->dev);
> -	struct rmi_device_platform_data *pdata = to_rmi_platform_data(rmi_dev);
>   	struct rmi_function *fn;
>   	int error;
>
> -	dev_dbg(dev, "Initializing F%02X for %s.\n",
> -		pdt->function_number, pdata->sensor_name);
> +	dev_dbg(dev, "Initializing F%02X\n", pdt->function_number);
>
>   	fn = kzalloc(sizeof(struct rmi_function), GFP_KERNEL);
>   	if (!fn) {
> @@ -822,8 +820,7 @@ static int rmi_driver_probe(struct device *dev)
>
>   	retval = rmi_scan_pdt(rmi_dev);
>   	if (retval) {
> -		dev_err(dev, "PDT scan for %s failed with code %d.\n",
> -			pdata->sensor_name, retval);
> +		dev_err(dev, "PDT scan failed with code %d.\n", retval);
>   		goto err_free_data;
>   	}
>
> diff --git a/drivers/input/rmi4/rmi_f11.c b/drivers/input/rmi4/rmi_f11.c
> index 4e0a296..553afd8 100644
> --- a/drivers/input/rmi4/rmi_f11.c
> +++ b/drivers/input/rmi4/rmi_f11.c
> @@ -1182,8 +1182,7 @@ static int rmi_f11_initialize(struct rmi_function *fn)
>   	struct f11_2d_sensor *sensor;
>   	u8 buf;
>
> -	dev_dbg(&fn->dev, "Initializing F11 values for %s.\n",
> -		 pdata->sensor_name);
> +	dev_dbg(&fn->dev, "Initializing F11 values.\n");
>
>   	/*
>   	** init instance data, fill in values and create any sysfs files
> diff --git a/drivers/input/rmi4/rmi_i2c.c b/drivers/input/rmi4/rmi_i2c.c
> index 24d8a04..910f05c 100644
> --- a/drivers/input/rmi4/rmi_i2c.c
> +++ b/drivers/input/rmi4/rmi_i2c.c
> @@ -196,8 +196,7 @@ static int rmi_i2c_probe(struct i2c_client *client,
>   		return -EINVAL;
>   	}
>
> -	dev_dbg(&client->dev, "Probing %s at %#02x (GPIO %d).\n",
> -		pdata->sensor_name ? pdata->sensor_name : "-no name-",
> +	dev_dbg(&client->dev, "Probing %#02x (GPIO %d).\n",
>   		client->addr, pdata->attn_gpio);
>
>   	if (!i2c_check_functionality(client->adapter, I2C_FUNC_I2C)) {
> diff --git a/include/linux/rmi.h b/include/linux/rmi.h
> index 735e978..65b59b5 100644
> --- a/include/linux/rmi.h
> +++ b/include/linux/rmi.h
> @@ -194,8 +194,6 @@ struct rmi_device_platform_data_spi {
>   /**
>    * struct rmi_device_platform_data - system specific configuration info.
>    *
> - * @sensor_name - this is used for various diagnostic messages.
> - *
>    * @firmware_name - if specified will override default firmware name,
>    * for reflashing.
>    *
> @@ -247,8 +245,6 @@ struct rmi_device_platform_data_spi {
>    * functions.
>    */
>   struct rmi_device_platform_data {
> -	char *sensor_name;	/* Used for diagnostics. */
> -
>   	int attn_gpio;
>   	enum rmi_attn_polarity attn_polarity;
>   	bool level_triggered;
>


-- 

Christopher Heiny
Senior Staff Firmware Engineer
Synaptics Incorporated

  parent reply	other threads:[~2014-02-04 23:08 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-24  0:00 [PATCH 00/15] Input: synaptics-rmi4 - cleanup and add DT support Courtney Cavin
2014-01-24  0:00 ` [PATCH 01/15] Input: synaptics-rmi4 - fix checkpatch.pl, sparse and GCC warnings Courtney Cavin
2014-01-24  0:00   ` [PATCH 02/15] Input: synaptics-rmi4 - don't kfree devm_ alloced memory Courtney Cavin
2014-01-24  0:00     ` [PATCH 03/15] Input: synaptics-rmi4 - don't free devices directly Courtney Cavin
2014-01-24  0:00       ` [PATCH 04/15] Input: synaptics-rmi4 - remove sensor name from platform data Courtney Cavin
2014-01-24  0:00         ` [PATCH 05/15] Input: synaptics-rmi4 - remove gpio handling and polling Courtney Cavin
2014-01-24  0:00           ` [PATCH 06/15] Input: synaptics-rmi4 - remove platform suspend callbacks Courtney Cavin
2014-01-24  0:00             ` [PATCH 07/15] Input: synaptics-rmi4 - remove remaining debugfs code Courtney Cavin
2014-01-24  0:00               ` [PATCH 08/15] Input: synaptics-rmi4 - cleanup platform data Courtney Cavin
2014-01-24  0:00                 ` [PATCH 09/15] Input: synaptics-rmi4 - remove unused defines and variables Courtney Cavin
2014-01-24  0:00                   ` [PATCH 10/15] Input: synaptics-rmi4 - add devicetree support Courtney Cavin
2014-01-24  0:00                     ` [PATCH 11/15] Input: synaptics-rmi4 - add regulator support Courtney Cavin
2014-01-24  0:00                       ` [PATCH 12/15] Input: synaptics-rmi4 - don't immediately set page on probe Courtney Cavin
2014-01-24  0:00                         ` [PATCH 13/15] Input: synaptics-rmi4 - properly set F01 container on PDT scan Courtney Cavin
2014-01-24  0:00                           ` [PATCH 14/15] Input: synaptics-rmi4 - ensure we have IRQs before reading status Courtney Cavin
2014-01-24  0:00                             ` [PATCH 15/15] Input: synaptics-rmi4 - correct RMI4 spec url Courtney Cavin
2014-02-04 23:10                               ` Christopher Heiny
2014-02-06  1:14                                 ` Dmitry Torokhov
2014-02-04 23:10                             ` [PATCH 14/15] Input: synaptics-rmi4 - ensure we have IRQs before reading status Christopher Heiny
2014-02-05  2:40                               ` Courtney Cavin
2014-02-04 23:10                           ` [PATCH 13/15] Input: synaptics-rmi4 - properly set F01 container on PDT scan Christopher Heiny
2014-02-05  2:39                             ` Courtney Cavin
2014-02-04 23:10                       ` [PATCH 11/15] Input: synaptics-rmi4 - add regulator support Christopher Heiny
2014-02-05  2:38                         ` Courtney Cavin
2014-02-04 23:10                     ` [PATCH 10/15] Input: synaptics-rmi4 - add devicetree support Christopher Heiny
2014-02-05  2:37                       ` Courtney Cavin
2014-02-04 23:10                   ` [PATCH 09/15] Input: synaptics-rmi4 - remove unused defines and variables Christopher Heiny
2014-02-05  2:35                     ` Courtney Cavin
2014-02-04 23:10                 ` [PATCH 08/15] Input: synaptics-rmi4 - cleanup platform data Christopher Heiny
2014-02-05  2:34                   ` Courtney Cavin
2014-02-04 23:09               ` [PATCH 07/15] Input: synaptics-rmi4 - remove remaining debugfs code Christopher Heiny
2014-02-05  2:33                 ` Courtney Cavin
2014-02-04 23:09             ` [PATCH 06/15] Input: synaptics-rmi4 - remove platform suspend callbacks Christopher Heiny
2014-02-05  2:32               ` Courtney Cavin
2014-02-04 23:08           ` [PATCH 05/15] Input: synaptics-rmi4 - remove gpio handling and polling Christopher Heiny
2014-02-05  2:31             ` Courtney Cavin
2014-02-06  9:28               ` Linus Walleij
2014-02-06 20:05                 ` Christopher Heiny
2014-02-07  1:45                   ` Courtney Cavin
2014-02-06 20:05               ` Christopher Heiny
2014-02-07  1:47                 ` Courtney Cavin
2014-02-04 23:08         ` Christopher Heiny [this message]
2014-02-05  2:30           ` [PATCH 04/15] Input: synaptics-rmi4 - remove sensor name from platform data Courtney Cavin
2014-02-04 23:08       ` [PATCH 03/15] Input: synaptics-rmi4 - don't free devices directly Christopher Heiny
2014-02-05  2:28         ` Courtney Cavin
2014-02-04 23:08     ` [PATCH 02/15] Input: synaptics-rmi4 - don't kfree devm_ alloced memory Christopher Heiny
2014-02-05  2:27       ` Courtney Cavin
2014-02-04 23:08   ` [PATCH 01/15] Input: synaptics-rmi4 - fix checkpatch.pl, sparse and GCC warnings Christopher Heiny
2014-02-05  2:26     ` Courtney Cavin
2014-02-06  1:09     ` Dmitry Torokhov
2014-02-06  1:36       ` Christopher Heiny
2014-02-13  6:36         ` Dmitry Torokhov
2014-02-13 18:56           ` Christopher Heiny
2014-02-13 19:10             ` Dmitry Torokhov
2014-02-13 19:12               ` Dmitry Torokhov
2014-02-13 19:25                 ` Christopher Heiny
2014-01-24  0:06 ` [PATCH 00/15] Input: synaptics-rmi4 - cleanup and add DT support Courtney Cavin
2014-01-24 23:24 ` Christopher Heiny
2014-01-25  1:08   ` Courtney Cavin

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=52F172ED.1040902@synaptics.com \
    --to=cheiny@synaptics.com \
    --cc=courtney.cavin@sonymobile.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.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;
as well as URLs for NNTP newsgroup(s).