From: Mark Roszko <mark.roszko-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Jean-Christophe PLAGNIOL-VILLARD
<plagnioj-sclMFOaUSTBWk0Htik3J/w@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
mailing list"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org,
Ludovic Desroches
<ludovic.desroches-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH v2] i2c:at91: Add device tree property to set clock-frequency
Date: Thu, 6 Mar 2014 23:26:45 -0500 [thread overview]
Message-ID: <CAJjB1qKriEVAQyvMaYu_N+QWJ=dzTxK91Hi_OUM8h_4i78EvbA@mail.gmail.com> (raw)
In-Reply-To: <4A1E236E-E048-4E37-AFE8-C0AC283B73D0-sclMFOaUSTBWk0Htik3J/w@public.gmane.org>
Unless I'm misunderstanding your reply, it doesn't need to be set on
each i2c device. It's meant to be an option to override the currently
hardcoded 100khz for all the at91 devices.
next prev parent reply other threads:[~2014-03-07 4:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 1:50 [PATCH v2] i2c:at91: Add device tree property to set clock-frequency Marek Roszko
[not found] ` <1393293045-31849-1-git-send-email-mark.roszko-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-02-28 11:05 ` Ludovic Desroches
2014-03-06 13:48 ` Mark Roszko
2014-03-07 3:51 ` Jean-Christophe PLAGNIOL-VILLARD
[not found] ` <4A1E236E-E048-4E37-AFE8-C0AC283B73D0-sclMFOaUSTBWk0Htik3J/w@public.gmane.org>
2014-03-07 4:26 ` Mark Roszko [this message]
2014-03-07 5:08 ` Jean-Christophe PLAGNIOL-VILLARD
[not found] ` <05EF9B59-7009-49D2-B57F-5612C39F1FF0-sclMFOaUSTBWk0Htik3J/w@public.gmane.org>
2014-03-07 5:30 ` Mark Roszko
2014-03-10 16: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='CAJjB1qKriEVAQyvMaYu_N+QWJ=dzTxK91Hi_OUM8h_4i78EvbA@mail.gmail.com' \
--to=mark.roszko-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ludovic.desroches-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org \
--cc=plagnioj-sclMFOaUSTBWk0Htik3J/w@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).