All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Arnaud Pouliquen <arnaud.pouliquen@st.com>
Cc: Robin Murphy <robin.murphy@arm.com>,
	Arnd Bergmann <arnd@arndb.de>, Mark Brown <broonie@kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	<linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Hartmut Knaack <knaack.h@gmx.de>,
	Alexandre Torgue <alexandre.torgue@st.com>
Subject: Re: [PATCH] IIO: ADC: stm32-dfsdm: avoid unused-variable warning
Date: Sun, 14 Jan 2018 12:07:16 +0000	[thread overview]
Message-ID: <20180114120716.320526c1@archlinux> (raw)
In-Reply-To: <838ace12-2722-33aa-0ed8-2e8e7494b2ae@st.com>

On Thu, 11 Jan 2018 18:38:49 +0100
Arnaud Pouliquen <arnaud.pouliquen@st.com> wrote:

> On 01/11/2018 03:27 PM, Robin Murphy wrote:
> > On 11/01/18 10:34, Arnd Bergmann wrote:  
> >> Building with CONFIG_OF disabled produces a compiler warning:
> >>
> >> drivers/iio/adc/stm32-dfsdm-core.c: In function 'stm32_dfsdm_probe':
> >> drivers/iio/adc/stm32-dfsdm-core.c:245:22: error: unused variable
> >> 'pnode' [-Werror=unused-variable]
> >>
> >> This removes the variable and open-codes it in the only place
> >> it gets used to avoid that warning.
> >>
> >> Fixes: bed73904e76f ("IIO: ADC: add stm32 DFSDM core support")
> >> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> >> ---
> >>   drivers/iio/adc/stm32-dfsdm-core.c | 3 +--
> >>   1 file changed, 1 insertion(+), 2 deletions(-)
> >>
> >> diff --git a/drivers/iio/adc/stm32-dfsdm-core.c
> >> b/drivers/iio/adc/stm32-dfsdm-core.c
> >> index 72427414db7f..6cd655f8239b 100644
> >> --- a/drivers/iio/adc/stm32-dfsdm-core.c
> >> +++ b/drivers/iio/adc/stm32-dfsdm-core.c
> >> @@ -242,7 +242,6 @@ MODULE_DEVICE_TABLE(of, stm32_dfsdm_of_match);
> >>   static int stm32_dfsdm_probe(struct platform_device *pdev)
> >>   {
> >>       struct dfsdm_priv *priv;
> >> -    struct device_node *pnode = pdev->dev.of_node;
> >>       const struct of_device_id *of_id;
> >>       const struct stm32_dfsdm_dev_data *dev_data;
> >>       struct stm32_dfsdm *dfsdm;
> >> @@ -254,7 +253,7 @@ static int stm32_dfsdm_probe(struct
> >> platform_device *pdev)
> >>         priv->pdev = pdev;
> >>   -    of_id = of_match_node(stm32_dfsdm_of_match, pnode);
> >> +    of_id = of_match_node(stm32_dfsdm_of_match, pdev->dev.of_node);
> >>       if (!of_id->data) {
> >>           dev_err(&pdev->dev, "Data associated to device is missing\n");
> >>           return -EINVAL;  
> > 
> > FWIW, it looks like this whole lot could be cleaned up by using
> > of_device_get_match_data().
> >   
> Right, and test of the return now seems to me an overprotection as data
> structure is defined in the driver...
> 
> Same optimization could be applied to stm32_dfsdm_adc_probe function.
> 
> Here is the patch I tested:

This looks like a good solution to me.

Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>

(given this should probably go on Mark's immutable branch).

Jonathan

> 
> ---
>  drivers/iio/adc/stm32-dfsdm-adc.c  | 9 +--------
>  drivers/iio/adc/stm32-dfsdm-core.c | 9 +--------
>  2 files changed, 2 insertions(+), 16 deletions(-)
> 
> diff --git a/drivers/iio/adc/stm32-dfsdm-adc.c
> b/drivers/iio/adc/stm32-dfsdm-adc.c
> index b03ca3f..01836c9 100644
> --- a/drivers/iio/adc/stm32-dfsdm-adc.c
> +++ b/drivers/iio/adc/stm32-dfsdm-adc.c
> @@ -1087,18 +1087,11 @@ static int stm32_dfsdm_adc_probe(struct
> platform_device *pdev)
>  	struct device_node *np = dev->of_node;
>  	const struct stm32_dfsdm_dev_data *dev_data;
>  	struct iio_dev *iio;
> -	const struct of_device_id *of_id;
>  	char *name;
>  	int ret, irq, val;
> 
> -	of_id = of_match_node(stm32_dfsdm_adc_match, np);
> -	if (!of_id->data) {
> -		dev_err(&pdev->dev, "Data associated to device is missing\n");
> -		return -EINVAL;
> -	}
> -
> -	dev_data = (const struct stm32_dfsdm_dev_data *)of_id->data;
> 
> +	dev_data = of_device_get_match_data(dev);
>  	iio = devm_iio_device_alloc(dev, sizeof(*adc));
>  	if (IS_ERR(iio)) {
>  		dev_err(dev, "%s: Failed to allocate IIO\n", __func__);
> diff --git a/drivers/iio/adc/stm32-dfsdm-core.c
> b/drivers/iio/adc/stm32-dfsdm-core.c
> index 7242741..6290332 100644
> --- a/drivers/iio/adc/stm32-dfsdm-core.c
> +++ b/drivers/iio/adc/stm32-dfsdm-core.c
> @@ -242,8 +242,6 @@ MODULE_DEVICE_TABLE(of, stm32_dfsdm_of_match);
>  static int stm32_dfsdm_probe(struct platform_device *pdev)
>  {
>  	struct dfsdm_priv *priv;
> -	struct device_node *pnode = pdev->dev.of_node;
> -	const struct of_device_id *of_id;
>  	const struct stm32_dfsdm_dev_data *dev_data;
>  	struct stm32_dfsdm *dfsdm;
>  	int ret;
> @@ -254,13 +252,8 @@ static int stm32_dfsdm_probe(struct platform_device
> *pdev)
> 
>  	priv->pdev = pdev;
> 
> -	of_id = of_match_node(stm32_dfsdm_of_match, pnode);
> -	if (!of_id->data) {
> -		dev_err(&pdev->dev, "Data associated to device is missing\n");
> -		return -EINVAL;
> -	}
> +	dev_data = of_device_get_match_data(&pdev->dev);
> 
> -	dev_data = (const struct stm32_dfsdm_dev_data *)of_id->data;
>  	dfsdm = &priv->dfsdm;
>  	dfsdm->fl_list = devm_kcalloc(&pdev->dev, dev_data->num_filters,
>  				      sizeof(*dfsdm->fl_list), GFP_KERNEL);


WARNING: multiple messages have this Message-ID (diff)
From: jic23@kernel.org (Jonathan Cameron)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] IIO: ADC: stm32-dfsdm: avoid unused-variable warning
Date: Sun, 14 Jan 2018 12:07:16 +0000	[thread overview]
Message-ID: <20180114120716.320526c1@archlinux> (raw)
In-Reply-To: <838ace12-2722-33aa-0ed8-2e8e7494b2ae@st.com>

On Thu, 11 Jan 2018 18:38:49 +0100
Arnaud Pouliquen <arnaud.pouliquen@st.com> wrote:

> On 01/11/2018 03:27 PM, Robin Murphy wrote:
> > On 11/01/18 10:34, Arnd Bergmann wrote:  
> >> Building with CONFIG_OF disabled produces a compiler warning:
> >>
> >> drivers/iio/adc/stm32-dfsdm-core.c: In function 'stm32_dfsdm_probe':
> >> drivers/iio/adc/stm32-dfsdm-core.c:245:22: error: unused variable
> >> 'pnode' [-Werror=unused-variable]
> >>
> >> This removes the variable and open-codes it in the only place
> >> it gets used to avoid that warning.
> >>
> >> Fixes: bed73904e76f ("IIO: ADC: add stm32 DFSDM core support")
> >> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> >> ---
> >> ? drivers/iio/adc/stm32-dfsdm-core.c | 3 +--
> >> ? 1 file changed, 1 insertion(+), 2 deletions(-)
> >>
> >> diff --git a/drivers/iio/adc/stm32-dfsdm-core.c
> >> b/drivers/iio/adc/stm32-dfsdm-core.c
> >> index 72427414db7f..6cd655f8239b 100644
> >> --- a/drivers/iio/adc/stm32-dfsdm-core.c
> >> +++ b/drivers/iio/adc/stm32-dfsdm-core.c
> >> @@ -242,7 +242,6 @@ MODULE_DEVICE_TABLE(of, stm32_dfsdm_of_match);
> >> ? static int stm32_dfsdm_probe(struct platform_device *pdev)
> >> ? {
> >> ????? struct dfsdm_priv *priv;
> >> -??? struct device_node *pnode = pdev->dev.of_node;
> >> ????? const struct of_device_id *of_id;
> >> ????? const struct stm32_dfsdm_dev_data *dev_data;
> >> ????? struct stm32_dfsdm *dfsdm;
> >> @@ -254,7 +253,7 @@ static int stm32_dfsdm_probe(struct
> >> platform_device *pdev)
> >> ? ????? priv->pdev = pdev;
> >> ? -??? of_id = of_match_node(stm32_dfsdm_of_match, pnode);
> >> +??? of_id = of_match_node(stm32_dfsdm_of_match, pdev->dev.of_node);
> >> ????? if (!of_id->data) {
> >> ????????? dev_err(&pdev->dev, "Data associated to device is missing\n");
> >> ????????? return -EINVAL;  
> > 
> > FWIW, it looks like this whole lot could be cleaned up by using
> > of_device_get_match_data().
> >   
> Right, and test of the return now seems to me an overprotection as data
> structure is defined in the driver...
> 
> Same optimization could be applied to stm32_dfsdm_adc_probe function.
> 
> Here is the patch I tested:

This looks like a good solution to me.

Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>

(given this should probably go on Mark's immutable branch).

Jonathan

> 
> ---
>  drivers/iio/adc/stm32-dfsdm-adc.c  | 9 +--------
>  drivers/iio/adc/stm32-dfsdm-core.c | 9 +--------
>  2 files changed, 2 insertions(+), 16 deletions(-)
> 
> diff --git a/drivers/iio/adc/stm32-dfsdm-adc.c
> b/drivers/iio/adc/stm32-dfsdm-adc.c
> index b03ca3f..01836c9 100644
> --- a/drivers/iio/adc/stm32-dfsdm-adc.c
> +++ b/drivers/iio/adc/stm32-dfsdm-adc.c
> @@ -1087,18 +1087,11 @@ static int stm32_dfsdm_adc_probe(struct
> platform_device *pdev)
>  	struct device_node *np = dev->of_node;
>  	const struct stm32_dfsdm_dev_data *dev_data;
>  	struct iio_dev *iio;
> -	const struct of_device_id *of_id;
>  	char *name;
>  	int ret, irq, val;
> 
> -	of_id = of_match_node(stm32_dfsdm_adc_match, np);
> -	if (!of_id->data) {
> -		dev_err(&pdev->dev, "Data associated to device is missing\n");
> -		return -EINVAL;
> -	}
> -
> -	dev_data = (const struct stm32_dfsdm_dev_data *)of_id->data;
> 
> +	dev_data = of_device_get_match_data(dev);
>  	iio = devm_iio_device_alloc(dev, sizeof(*adc));
>  	if (IS_ERR(iio)) {
>  		dev_err(dev, "%s: Failed to allocate IIO\n", __func__);
> diff --git a/drivers/iio/adc/stm32-dfsdm-core.c
> b/drivers/iio/adc/stm32-dfsdm-core.c
> index 7242741..6290332 100644
> --- a/drivers/iio/adc/stm32-dfsdm-core.c
> +++ b/drivers/iio/adc/stm32-dfsdm-core.c
> @@ -242,8 +242,6 @@ MODULE_DEVICE_TABLE(of, stm32_dfsdm_of_match);
>  static int stm32_dfsdm_probe(struct platform_device *pdev)
>  {
>  	struct dfsdm_priv *priv;
> -	struct device_node *pnode = pdev->dev.of_node;
> -	const struct of_device_id *of_id;
>  	const struct stm32_dfsdm_dev_data *dev_data;
>  	struct stm32_dfsdm *dfsdm;
>  	int ret;
> @@ -254,13 +252,8 @@ static int stm32_dfsdm_probe(struct platform_device
> *pdev)
> 
>  	priv->pdev = pdev;
> 
> -	of_id = of_match_node(stm32_dfsdm_of_match, pnode);
> -	if (!of_id->data) {
> -		dev_err(&pdev->dev, "Data associated to device is missing\n");
> -		return -EINVAL;
> -	}
> +	dev_data = of_device_get_match_data(&pdev->dev);
> 
> -	dev_data = (const struct stm32_dfsdm_dev_data *)of_id->data;
>  	dfsdm = &priv->dfsdm;
>  	dfsdm->fl_list = devm_kcalloc(&pdev->dev, dev_data->num_filters,
>  				      sizeof(*dfsdm->fl_list), GFP_KERNEL);

  reply	other threads:[~2018-01-14 12:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-11 10:34 [PATCH] IIO: ADC: stm32-dfsdm: avoid unused-variable warning Arnd Bergmann
2018-01-11 10:34 ` Arnd Bergmann
2018-01-11 14:27 ` Robin Murphy
2018-01-11 14:27   ` Robin Murphy
2018-01-11 17:38   ` Arnaud Pouliquen
2018-01-11 17:38     ` Arnaud Pouliquen
2018-01-14 12:07     ` Jonathan Cameron [this message]
2018-01-14 12:07       ` Jonathan Cameron

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=20180114120716.320526c1@archlinux \
    --to=jic23@kernel.org \
    --cc=alexandre.torgue@st.com \
    --cc=arnaud.pouliquen@st.com \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=pmeerw@pmeerw.net \
    --cc=robin.murphy@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.