linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shevchenko, Andriy" <andriy.shevchenko@intel.com>
To: "lee.jones@linaro.org" <lee.jones@linaro.org>
Cc: "mturquette@linaro.org" <mturquette@linaro.org>,
	"sameo@linux.intel.com" <sameo@linux.intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Chen, Alvin" <alvin.chen@intel.com>,
	"Tan, Raymond" <raymond.tan@intel.com>
Subject: Re: [PATCH v3 1/1] mfd: intel_quark_i2c_gpio: Add Intel Quark X1000 I2C-GPIO MFD Driver
Date: Tue, 20 Jan 2015 16:10:31 +0000	[thread overview]
Message-ID: <1421770235.31903.95.camel@intel.com> (raw)
In-Reply-To: <20150120155453.GJ13701@x1>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1488 bytes --]

On Tue, 2015-01-20 at 15:54 +0000, Lee Jones wrote:
> On Tue, 20 Jan 2015, Shevchenko, Andriy wrote:
> 
> > On Tue, 2015-01-20 at 12:47 +0000, Lee Jones wrote:
> > > On Thu, 11 Dec 2014, Raymond Tan wrote:
> > 
> > []
> > 
> > > > +static const struct i2c_mode_info platform_i2c_mode_info[] = {
> > > > +	{
> > > > +		.name = "Galileo",
> > > > +		.i2c_scl_freq = 100000,
> > > > +	},
> > > > +	{
> > > > +		.name = "GalileoGen2",
> > > > +		.i2c_scl_freq = 400000,
> > > > +	},
> > > > +};
> > > 
> > > We normally do not capitalise device names.
> > 
> > This comes from DMI, so, can't be altered I suppose.
> 
> I'm not sure what that means, but sounds reasonable.

http://en.wikipedia.org/wiki/Desktop_Management_Interface

In short, it comes from firmware that's why we have to use exact names
here.


-- 
Andy Shevchenko <andriy.shevchenko@intel.com>
Intel Finland Oy
---------------------------------------------------------------------
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki 
Business Identity Code: 0357606 - 4 
Domiciled in Helsinki 

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

  reply	other threads:[~2015-01-20 16:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11  9:38 [PATCH v3 0/1] mfd: intel_quark_i2c_gpio: Add Intel Quark X1000 I2C-GPIO MFD Driver Raymond Tan
2014-12-11  9:38 ` [PATCH v3 1/1] " Raymond Tan
2014-12-11 10:27   ` Shevchenko, Andriy
2015-01-06  3:13     ` Tan, Raymond
2015-01-20 12:26       ` Lee Jones
2014-12-11 22:26   ` Mike Turquette
2014-12-22  2:33     ` Tan, Raymond
2015-01-20 17:30       ` Mike Turquette
2015-01-26 14:28         ` Tan, Raymond
2015-01-20 12:47   ` Lee Jones
2015-01-20 13:41     ` Shevchenko, Andriy
2015-01-20 15:54       ` Lee Jones
2015-01-20 16:10         ` Shevchenko, Andriy [this message]
2015-01-20 17:31     ` Mike Turquette

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=1421770235.31903.95.camel@intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=alvin.chen@intel.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@linaro.org \
    --cc=raymond.tan@intel.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;
as well as URLs for NNTP newsgroup(s).