From: Raymond Tan <raymond.tan-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Romain Baeriswyl
<romainba-ux6zf3SgZrrQT0dZR+AlfA@public.gmane.org>
Subject: [PATCH 0/1] i2c: designware: Add support for Intel Quark X1000
Date: Wed, 3 Sep 2014 10:41:37 +0800 [thread overview]
Message-ID: <1409712098-13997-1-git-send-email-raymond.tan@intel.com> (raw)
From: "Tan, Raymond" <raymond.tan-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Hi,
This patch is for enabling support of Intel Quark X1000 i2c controller. The
Quark designware i2c controller is registered as a MFD device, and Quark
exports a single PCI device with both I2C and GPIO functions.
In Quark, there is currently no other configuration mechanism other than
board files to configure the I2C mode for the the controller.
This patch is built upon the changes made by Romain Baeriswyl, titled
[PATCH V3 2/2] i2c designware add support of I2C standard mode, at
https://lkml.org/lkml/2014/3/25/135
Tan, Raymond (1):
i2c: designware: add support of platform data to set I2C mode
drivers/i2c/busses/i2c-designware-platdrv.c | 6 ++++++
include/linux/platform_data/i2c-designware.h | 21 +++++++++++++++++++++
2 files changed, 27 insertions(+)
create mode 100644 include/linux/platform_data/i2c-designware.h
--
1.7.9.5
next reply other threads:[~2014-09-03 2:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 2:41 Raymond Tan [this message]
[not found] ` <1409712098-13997-1-git-send-email-raymond.tan-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-09-03 2:41 ` [PATCH 1/1] i2c: designware: add support of platform data to set I2C mode Raymond Tan
[not found] ` <1409712098-13997-2-git-send-email-raymond.tan-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-09-20 9:29 ` Wolfram Sang
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=1409712098-13997-1-git-send-email-raymond.tan@intel.com \
--to=raymond.tan-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=romainba-ux6zf3SgZrrQT0dZR+AlfA@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.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;
as well as URLs for NNTP newsgroup(s).