public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: patches@opensource.wolfsonmicro.com,
	linux-kernel@vger.kernel.org, rf@opensource.wolfsonmicro.com,
	sameo@linux.intel.com
Subject: Re: [PATCH v2 6/6] mfd: arizona: use correct type ID for device tree config
Date: Tue, 13 Oct 2015 10:25:13 +0100	[thread overview]
Message-ID: <20151013092512.GR32409@x1> (raw)
In-Reply-To: <1443788955-7523-6-git-send-email-ckeepax@opensource.wolfsonmicro.com>

On Fri, 02 Oct 2015, Charles Keepax wrote:

> From: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
> 
> In the case of a device tree config the code uses the device ID
> from the DT entry to check which codec is required but when storing
> the ID into struct arizona it was always using the non-DT SPI device
> table to get an ID.
> 
> This patch changes the code to store the correct ID into struct arizona.
> 
> Signed-off-by: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
> Acked-by: Lee Jones <lee.jones@linaro.org>
> Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> ---
>  drivers/mfd/arizona-i2c.c |    5 ++---
>  drivers/mfd/arizona-spi.c |    5 ++---
>  2 files changed, 4 insertions(+), 6 deletions(-)

Applied, thanks.

> diff --git a/drivers/mfd/arizona-i2c.c b/drivers/mfd/arizona-i2c.c
> index 914bdce..4e3afd1 100644
> --- a/drivers/mfd/arizona-i2c.c
> +++ b/drivers/mfd/arizona-i2c.c
> @@ -56,8 +56,7 @@ static int arizona_i2c_probe(struct i2c_client *i2c,
>  			regmap_config = &wm8998_i2c_regmap;
>  		break;
>  	default:
> -		dev_err(&i2c->dev, "Unknown device type %ld\n",
> -			id->driver_data);
> +		dev_err(&i2c->dev, "Unknown device type %ld\n", type);
>  		return -EINVAL;
>  	}
>  
> @@ -79,7 +78,7 @@ static int arizona_i2c_probe(struct i2c_client *i2c,
>  		return ret;
>  	}
>  
> -	arizona->type = id->driver_data;
> +	arizona->type = type;
>  	arizona->dev = &i2c->dev;
>  	arizona->irq = i2c->irq;
>  
> diff --git a/drivers/mfd/arizona-spi.c b/drivers/mfd/arizona-spi.c
> index 850a63a..8cffb1c 100644
> --- a/drivers/mfd/arizona-spi.c
> +++ b/drivers/mfd/arizona-spi.c
> @@ -47,8 +47,7 @@ static int arizona_spi_probe(struct spi_device *spi)
>  			regmap_config = &wm5110_spi_regmap;
>  		break;
>  	default:
> -		dev_err(&spi->dev, "Unknown device type %ld\n",
> -			id->driver_data);
> +		dev_err(&spi->dev, "Unknown device type %ld\n", type);
>  		return -EINVAL;
>  	}
>  
> @@ -70,7 +69,7 @@ static int arizona_spi_probe(struct spi_device *spi)
>  		return ret;
>  	}
>  
> -	arizona->type = id->driver_data;
> +	arizona->type = type;
>  	arizona->dev = &spi->dev;
>  	arizona->irq = spi->irq;
>  

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2015-10-13  9:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02 12:29 [PATCH v2 1/6] mfd: arizona: factor out DCVDD isolation control Charles Keepax
2015-10-02 12:29 ` [PATCH v2 2/6] mfd: arizona: factor out checking of jack detection state Charles Keepax
2015-10-13  9:24   ` Lee Jones
2015-10-02 12:29 ` [PATCH v2 3/6] mfd: arizona: Downgrade type mismatch messages to dev_warn Charles Keepax
2015-10-13  9:24   ` Lee Jones
2015-10-02 12:29 ` [PATCH v2 4/6] mfd: arizona: Simplify adding subdevices Charles Keepax
2015-10-13  9:24   ` Lee Jones
2015-10-02 12:29 ` [PATCH v2 5/6] mfd: arizona: Remove use of codec build config #ifdefs Charles Keepax
2015-10-13  9:23   ` Lee Jones
2015-10-13  9:25   ` Lee Jones
2015-10-02 12:29 ` [PATCH v2 6/6] mfd: arizona: use correct type ID for device tree config Charles Keepax
2015-10-13  9:25   ` Lee Jones [this message]
2015-10-13  9:23 ` [PATCH v2 1/6] mfd: arizona: factor out DCVDD isolation control Lee Jones

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=20151013092512.GR32409@x1 \
    --to=lee.jones@linaro.org \
    --cc=ckeepax@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@opensource.wolfsonmicro.com \
    --cc=rf@opensource.wolfsonmicro.com \
    --cc=sameo@linux.intel.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