Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1237485
| From | Lee Jones <lee.jones@linaro.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v2 3/8] mfd: intel_quark_i2c_gpio: load gpio driver first |
| Date | 2015-10-01 17:00 +0200 |
| Message-ID | <qeNuX-7IQ-29@gated-at.bofh.it> (permalink) |
| References | <qeKdH-2A1-3@gated-at.bofh.it> <qeKdJ-2A1-41@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, 01 Oct 2015, Andy Shevchenko wrote:
> On Intel Galileo boards the GPIO expander is connected to i2c bus. Moreover it
> is able to generate interrupt, but interrupt line is connected to GPIO. That's
> why we have to have GPIO driver in place when we will probe i2c host with
> device connected to it.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> drivers/mfd/intel_quark_i2c_gpio.c | 19 +++++++++----------
> 1 file changed, 9 insertions(+), 10 deletions(-)
Acked-by: Lee Jones <lee.jones@linaro.org>
Are there build dependancies in this set? Or can all patches filter
through their own subsystems?
> diff --git a/drivers/mfd/intel_quark_i2c_gpio.c b/drivers/mfd/intel_quark_i2c_gpio.c
> index 1ce1603..958c134 100644
> --- a/drivers/mfd/intel_quark_i2c_gpio.c
> +++ b/drivers/mfd/intel_quark_i2c_gpio.c
> @@ -90,19 +90,19 @@ static struct resource intel_quark_gpio_res[] = {
>
> static struct mfd_cell intel_quark_mfd_cells[] = {
> {
> - .id = MFD_I2C_BAR,
> - .name = "i2c_designware",
> - .num_resources = ARRAY_SIZE(intel_quark_i2c_res),
> - .resources = intel_quark_i2c_res,
> - .ignore_resource_conflicts = true,
> - },
> - {
> .id = MFD_GPIO_BAR,
> .name = "gpio-dwapb",
> .num_resources = ARRAY_SIZE(intel_quark_gpio_res),
> .resources = intel_quark_gpio_res,
> .ignore_resource_conflicts = true,
> },
> + {
> + .id = MFD_I2C_BAR,
> + .name = "i2c_designware",
> + .num_resources = ARRAY_SIZE(intel_quark_i2c_res),
> + .resources = intel_quark_i2c_res,
> + .ignore_resource_conflicts = true,
> + },
> };
>
> static const struct pci_device_id intel_quark_mfd_ids[] = {
> @@ -248,12 +248,11 @@ static int intel_quark_mfd_probe(struct pci_dev *pdev,
>
> dev_set_drvdata(&pdev->dev, quark_mfd);
>
> - ret = intel_quark_i2c_setup(pdev, &intel_quark_mfd_cells[MFD_I2C_BAR]);
> + ret = intel_quark_i2c_setup(pdev, &intel_quark_mfd_cells[1]);
> if (ret)
> return ret;
>
> - ret = intel_quark_gpio_setup(pdev,
> - &intel_quark_mfd_cells[MFD_GPIO_BAR]);
> + ret = intel_quark_gpio_setup(pdev, &intel_quark_mfd_cells[0]);
> if (ret)
> return ret;
>
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH v2 0/8] enable I2C devices behind I2C bus on Gen2 Andy Shevchenko <andriy.shevchenko@linux.intel.com> - 2015-10-01 13:30 +0200
[PATCH v2 3/8] mfd: intel_quark_i2c_gpio: load gpio driver first Andy Shevchenko <andriy.shevchenko@linux.intel.com> - 2015-10-01 13:30 +0200
Re: [PATCH v2 3/8] mfd: intel_quark_i2c_gpio: load gpio driver first Lee Jones <lee.jones@linaro.org> - 2015-10-01 17:00 +0200
Re: [PATCH v2 3/8] mfd: intel_quark_i2c_gpio: load gpio driver first Andy Shevchenko <andriy.shevchenko@linux.intel.com> - 2015-10-02 14:20 +0200
Re: [PATCH v2 0/8] enable I2C devices behind I2C bus on Gen2 Linus Walleij <linus.walleij@linaro.org> - 2015-10-05 09:30 +0200
Re: [PATCH v2 0/8] enable I2C devices behind I2C bus on Gen2 Andy Shevchenko <andriy.shevchenko@linux.intel.com> - 2015-10-05 09:40 +0200
csiph-web