From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Jan Kiszka <jan.kiszka@siemens.com>,
Lee Jones <lee.jones@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mfd: intel_quark_i2c_gpio: Add support for SIMATIC IOT2000 platform
Date: Tue, 09 May 2017 14:34:52 +0300 [thread overview]
Message-ID: <1494329692.30052.75.camel@linux.intel.com> (raw)
In-Reply-To: <80e73378-83d9-b61e-670d-6cd7372171c2@siemens.com>
On Tue, 2017-05-09 at 06:40 +0200, Jan Kiszka wrote:
> The SIMATIC IOT2000 is derived from the Galileo Gen2 board and shares
> its I2C frequency.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> Signed-off-by: Sascha Weisenberger <sascha.weisenberger@siemens.com>
Hmm... I thought that SoB chain goes from first author to last. (Or in
case of maintainer / submitter their SoB goes at the end, which is
apparently not the case here).
Other than above
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>
> ---
> drivers/mfd/intel_quark_i2c_gpio.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/mfd/intel_quark_i2c_gpio.c
> b/drivers/mfd/intel_quark_i2c_gpio.c
> index 7946d6e38b87..98dddf2831ad 100644
> --- a/drivers/mfd/intel_quark_i2c_gpio.c
> +++ b/drivers/mfd/intel_quark_i2c_gpio.c
> @@ -72,6 +72,10 @@ static const struct i2c_mode_info
> platform_i2c_mode_info[] = {
> .name = "GalileoGen2",
> .i2c_scl_freq = 400000,
> },
> + {
> + .name = "SIMATIC IOT2000",
> + .i2c_scl_freq = 400000,
> + },
> {}
> };
>
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-05-09 11:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 4:40 [PATCH] mfd: intel_quark_i2c_gpio: Add support for SIMATIC IOT2000 platform Jan Kiszka
2017-05-09 11:34 ` Andy Shevchenko [this message]
2017-05-12 8:12 ` Lee Jones
2017-05-19 7:55 ` Jan Kiszka
2017-05-19 14:22 ` Andy Shevchenko
2017-05-19 14:35 ` Jan Kiszka
2017-05-22 9:36 ` 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=1494329692.30052.75.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=jan.kiszka@siemens.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
/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