public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: York Sun <yorksun@freescale.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: <linux-kernel@vger.kernel.org>, <linux-i2c@vger.kernel.org>,
	"Peter Korsgaard" <peter.korsgaard@barco.com>
Subject: Re: [PATCH] driver/i2c/mux: Add register based mux i2c-mux-reg
Date: Mon, 17 Aug 2015 09:37:29 -0700	[thread overview]
Message-ID: <55D20DC9.2060304@freescale.com> (raw)
In-Reply-To: <20150815202302.GB3463@katana>



On 08/15/2015 01:23 PM, Wolfram Sang wrote:
> On Tue, Jun 16, 2015 at 10:28:12AM -0700, York Sun wrote:
>> Based on i2c-mux-gpio driver, similarly the register based mux
>> switch from one bus to another by setting a single register.
>> The register can be on PCIe bus, local bus, or any memory-mapped
>> address.
>>
>> Signed-off-by: York Sun <yorksun@freescale.com>
>> CC: Wolfram Sang <wsa@the-dreams.de>
>> CC: Peter Korsgaard <peter.korsgaard@barco.com>
> 
> Mostly good.
> 
>> +static int i2c_mux_reg_probe(struct platform_device *pdev)
>> +{
>> +	struct regmux *mux;
>> +	struct i2c_adapter *parent;
>> +	struct resource *res;
>> +	int (*deselect)(struct i2c_adapter *, void *, u32);
>> +	unsigned int initial_state, class;
> 
> gcc says:
> 
> drivers/i2c/muxes/i2c-mux-reg.c:182:15: warning: variable 'initial_state' set but not used [-Wunused-but-set-variable]
> 
> It seens you prepared for setting the initial state but don't do the
> actual set?

Thanks for catching this. I set the initial state variable but used another
variable when it is actually used. Kernel Makefile disables
unused-but-set-variable by default. How did you enable this warning without
being flooded by the warnings? (I tried W=1)

> 
>> +static struct platform_driver i2c_mux_reg_driver = {
>> +	.probe	= i2c_mux_reg_probe,
>> +	.remove	= i2c_mux_reg_remove,
>> +	.driver	= {
>> +		.owner	= THIS_MODULE,
> 
> coccicheck says:
> 
> drivers/i2c/muxes/i2c-mux-reg.c:288:3-8: No need to set .owner here. The core will do it.

Will drop it in next version.

York

  reply	other threads:[~2015-08-17 16:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-16 17:28 [PATCH] driver/i2c/mux: Add register based mux i2c-mux-reg York Sun
2015-06-17  8:54 ` Paul Bolle
2015-06-17 15:00   ` Alexander Sverdlin
2015-06-17 16:03     ` Paul Bolle
2015-06-18  7:40       ` Alexander Sverdlin
2015-06-18  8:08         ` Paul Bolle
2015-06-18  9:04           ` Alexander Sverdlin
2015-06-18  9:32             ` Paul Bolle
2015-06-18  9:42               ` Alexander Sverdlin
2015-06-18  9:55                 ` Paul Bolle
2015-06-17 15:03 ` Alexander Sverdlin
2015-06-17 16:43   ` York Sun
2015-06-18  7:58     ` Alexander Sverdlin
2015-08-15 20:23 ` Wolfram Sang
2015-08-17 16:37   ` York Sun [this message]
2015-08-18 16:44     ` Wolfram Sang

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=55D20DC9.2060304@freescale.com \
    --to=yorksun@freescale.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.korsgaard@barco.com \
    --cc=wsa@the-dreams.de \
    /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