From: viresh.kumar@st.com (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: Update comment for clk_round_rate()
Date: Thu, 5 Apr 2012 12:37:24 +0530 [thread overview]
Message-ID: <4F7D44AC.6040605@st.com> (raw)
In-Reply-To: <20120405070324.GB27274@pengutronix.de>
On 4/5/2012 12:33 PM, Uwe Kleine-K?nig wrote:
> It depends on your scenario. E.g. for an UART clock it might be better
> to choose 130. Here choosing the frequency is not about a fixed maximum
> but to match the sample rate of the device connect to your UART.
My point was: we can almost always guarantee that device will still
be operational at any frequency below the one requested. But it may
not work at any freq above the requested one. So, giving 130 here may
break it.
--
viresh
next prev parent reply other threads:[~2012-04-05 7:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 17:27 [PATCH] clk: Update comment for clk_round_rate() viresh kumar
2012-04-04 18:07 ` Turquette, Mike
2012-04-05 5:11 ` Viresh Kumar
2012-04-05 7:03 ` Uwe Kleine-König
2012-04-05 7:07 ` Viresh Kumar [this message]
2012-04-05 7:26 ` Uwe Kleine-König
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=4F7D44AC.6040605@st.com \
--to=viresh.kumar@st.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.