From: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH v2] i2c: aspeed: fix invalid clock parameters for very large divisors
Date: Fri, 21 Sep 2018 15:26:13 -0700 [thread overview]
Message-ID: <f5943177-6f1b-9344-3821-2aac001ff45d@linux.intel.com> (raw)
In-Reply-To: <20180921221025.75003-1-brendanhiggins@google.com>
Hi,
On 9/21/2018 3:10 PM, Brendan Higgins wrote:
> The function that computes clock parameters from divisors did not
> respect the maximum size of the bitfields that the parameters were
> written to. This fixes the bug.
>
> This bug can be reproduced with (and this fix verified with) the test
> at: https://kunit-review.googlesource.com/c/linux/+/1035/
>
> Discovered-by-KUnit: https://kunit-review.googlesource.com/c/linux/+/1035/
> Signed-off-by: Brendan Higgins <brendanhiggins@google.com>
> Reviewed-by: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
> ---
> - v2 updates the title of the patch, renames a local variable, and
> prints an error when the clock divider is clamped.
> ---
[....]
> + if (base_clk_divisor > ASPEED_I2CD_TIME_BASE_DIVISOR_MASK) {
> + base_clk_divisor = ASPEED_I2CD_TIME_BASE_DIVISOR_MASK;
> + clk_low = clk_high_low_mask;
> + clk_high = clk_high_low_mask;
> + dev_err(dev,
> + "clamping clock divider: divider requested, %u, is greater than largest possible divider, %u.",
Please put a newline character at the end of the string.
Thanks,
Jae
[....]
next prev parent reply other threads:[~2018-09-21 22:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 22:10 [PATCH v2] i2c: aspeed: fix invalid clock parameters for very large divisors Brendan Higgins
2018-09-21 22:26 ` Jae Hyun Yoo [this message]
2018-09-21 22:30 ` Brendan Higgins
2018-09-22 14:16 ` Joe Perches
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=f5943177-6f1b-9344-3821-2aac001ff45d@linux.intel.com \
--to=jae.hyun.yoo@linux.intel.com \
--cc=linux-aspeed@lists.ozlabs.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