From: Max Filippov <jcmvbkbc-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Peter Korsgaard <jacmet-OfajU3CKLf1/SzgSGea1oA@public.gmane.org>
Cc: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Max Filippov <jcmvbkbc-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: [PATCH v2 0/2] i2c: i2c-ocores: clock improvements
Date: Mon, 2 Feb 2015 18:28:11 +0300 [thread overview]
Message-ID: <1422890893-30989-1-git-send-email-jcmvbkbc@gmail.com> (raw)
Peter, Wolfram,
this series fixes clock-frequency attribute usage by i2c-ocores driver and
adds optional common clock framework support.
Changes v1->v2:
- add cleanup patch for clock-frequency attribute that implements options
2 and 3, as was suggested here: https://lkml.org/lkml/2015/1/22/527
- make CCF support optional
Max Filippov (2):
i2c: i2c-ocores: fix clock-frequency binding usage
i2c: i2c-ocores: add common clock support
.../devicetree/bindings/i2c/i2c-ocores.txt | 42 +++++++++-
drivers/i2c/busses/i2c-ocores.c | 95 +++++++++++++++++++---
2 files changed, 122 insertions(+), 15 deletions(-)
--
1.8.1.4
next reply other threads:[~2015-02-02 15:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 15:28 Max Filippov [this message]
2015-02-02 15:28 ` [PATCH v2 1/2] i2c: i2c-ocores: fix clock-frequency binding usage Max Filippov
2015-02-05 19:11 ` Wolfram Sang
2015-02-05 19:46 ` Max Filippov
2015-02-05 19:51 ` Wolfram Sang
2015-02-02 15:28 ` [PATCH v2 2/2] i2c: i2c-ocores: add common clock support Max Filippov
[not found] ` <1422890893-30989-3-git-send-email-jcmvbkbc-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-02-05 19:15 ` Wolfram Sang
2015-02-05 19:24 ` Max Filippov
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=1422890893-30989-1-git-send-email-jcmvbkbc@gmail.com \
--to=jcmvbkbc-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=jacmet-OfajU3CKLf1/SzgSGea1oA@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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).