From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>, linux-kernel@vger.kernel.org
Cc: Lee Jones <lee.jones@linaro.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Johannes Stezenbach <js@sig21.net>,
linux-input@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH 1/3] mfd: Add support for Cherry Trail Dollar Cove TI PMIC
Date: Tue, 22 Aug 2017 12:37:45 +0300 [thread overview]
Message-ID: <1503394665.25945.43.camel@linux.intel.com> (raw)
In-Reply-To: <20170822055710.26515-2-tiwai@suse.de>
On Tue, 2017-08-22 at 07:57 +0200, Takashi Iwai wrote:
> This patch adds the MFD driver for Dollar Cove TI PMIC (ACPI INT33F5)
> that is found on some Intel Cherry Trail devices.
> The driver is based on the original work by Intel, found at:
> https://github.com/01org/ProductionKernelQuilts
>
> This is a minimal version for adding the basic resources. Currently,
> only ACPI PMIC opregion and the external power-button are used.
Overall looks good. Few comments below.
I hope Hans de Goede had been involved somehow to this. He did enormous
work to examine all this PMIC/ACPI/I2C stuff on CHT platforms.
> +#include <linux/module.h>
> +#include <linux/mfd/core.h>
> +#include <linux/i2c.h>
> +#include <linux/interrupt.h>
> +#include <linux/gpio/consumer.h>
> +#include <linux/acpi.h>
> +#include <linux/regmap.h>
> +#include <linux/mfd/intel_soc_pmic.h>
Alphabetical order?
> +static const struct i2c_device_id dc_ti_i2c_id[] = {
> + { }
> +};
No need anymore. Moreover, you already are using ->probe_new().
> +static struct i2c_driver dc_ti_i2c_driver = {
> + .driver = {
> + .name = KBUILD_MODNAME,
> + .pm = &dc_ti_pm_ops,
> + .acpi_match_table = ACPI_PTR(dc_ti_acpi_ids),
ACPI_PTR is redundant here, driver is solely for ACPI case.
> + },
> + .probe_new = dc_ti_probe,
> + .shutdown = dc_ti_shutdown,
> + .id_table = dc_ti_i2c_id,
> +};
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-08-22 9:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 5:57 [PATCH 0/3] Dollar Cove TI PMIC support for Intel Cherry Trail Takashi Iwai
2017-08-22 5:57 ` [PATCH 1/3] mfd: Add support for Cherry Trail Dollar Cove TI PMIC Takashi Iwai
2017-08-22 9:37 ` Andy Shevchenko [this message]
2017-08-22 10:27 ` Takashi Iwai
2017-08-22 5:57 ` [PATCH 2/3] input/keyboard: Add support for Dollar Cove TI power button Takashi Iwai
2017-08-22 9:42 ` Andy Shevchenko
2017-08-22 10:58 ` Takashi Iwai
2017-08-22 17:25 ` Johannes Stezenbach
2017-08-31 18:33 ` Dmitry Torokhov
2017-08-31 20:34 ` Takashi Iwai
2017-09-01 11:09 ` Andy Shevchenko
2017-09-01 12:12 ` Takashi Iwai
2017-08-22 5:57 ` [PATCH 3/3] ACPI / PMIC: Add opregion driver for Intel Dollar Cove TI PMIC Takashi Iwai
2017-08-22 9:58 ` Andy Shevchenko
2017-08-22 10:25 ` Takashi Iwai
2017-08-22 11:01 ` Takashi Iwai
2017-08-22 11:37 ` Andy Shevchenko
2017-08-22 12:06 ` Takashi Iwai
2017-08-22 12:08 ` Andy Shevchenko
2017-08-22 12:26 ` Takashi Iwai
2017-08-22 13:26 ` Andy Shevchenko
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=1503394665.25945.43.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=js@sig21.net \
--cc=lee.jones@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
--cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).