From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Raymond Tan <raymond.tan-ral2JQCrhuEAvxtiuMwx3w@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: Re: [PATCH 1/1] i2c: designware: add support of platform data to set I2C mode
Date: Sat, 20 Sep 2014 11:29:09 +0200 [thread overview]
Message-ID: <20140920092909.GE1612@katana> (raw)
In-Reply-To: <1409712098-13997-2-git-send-email-raymond.tan-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 691 bytes --]
On Wed, Sep 03, 2014 at 10:41:38AM +0800, Raymond Tan wrote:
> From: "Tan, Raymond" <raymond.tan-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
>
> Use the platform data to set the clk_freq when there is no DT configuration
> available. The clk_freq in turn will determine the I2C speed mode.
>
> In Quark, there is currently no other configuration mechanism other than
> board files.
>
> Signed-off-by: Raymond Tan <raymond.tan-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> Reviewed-by: Mika Westerberg <mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
> Reviewed-by: Hock Leong Kweh <hock.leong.kweh-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Applied to for-next, thanks!
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-09-20 9:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 2:41 [PATCH 0/1] i2c: designware: Add support for Intel Quark X1000 Raymond Tan
[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 [this message]
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=20140920092909.GE1612@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=raymond.tan-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=romainba-ux6zf3SgZrrQT0dZR+AlfA@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).