[Armadeus-commitlog] armadeus branch, master, updated. armadeus-6.0-51-gb007f87

[Fabien M <fa...@us...>]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "armadeus".

The branch, master has been updated
       via  b007f87606033757c68bf6a91e9dee8437b9ff59 (commit)
      from  bbbf0f462c4b4542533eaf1b96ae00918de7ba70 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit b007f87606033757c68bf6a91e9dee8437b9ff59
Author: Fabien Marteau <fab...@ar...>
Date:   Thu Mar 31 09:44:54 2016 +0200

    [LINUX] patch 0447 useless (included in kernel 4.4)

-----------------------------------------------------------------------

Summary of changes:
 ...g-pwm-mxs-fixes-bug-in-period-computation.patch |   55 --------------------
 1 files changed, 0 insertions(+), 55 deletions(-)
 delete mode 100644 patches/linux/4.4/0447-induct-hug-pwm-mxs-fixes-bug-in-period-computation.patch

diff --git a/patches/linux/4.4/0447-induct-hug-pwm-mxs-fixes-bug-in-period-computation.patch b/patches/linux/4.4/0447-induct-hug-pwm-mxs-fixes-bug-in-period-computation.patch
deleted file mode 100644
index 82cdcb6..0000000
--- a/patches/linux/4.4/0447-induct-hug-pwm-mxs-fixes-bug-in-period-computation.patch
+++ /dev/null
@@ -1,55 +0,0 @@
-Date: Tue, 27 Jan 2015 14:37:42 +0100
-From: Gaetan Hug <gh...@in...>
-To: Armadeus Forum ML <arm...@li...>,
-	<lin...@vg...>
-Subject: [Armadeus-forum] Found bug in pwm-mxs.c
-
-Hello folks,
-
-   I found a bug in the pwm-mxs.c driver for the i.MX28 platform.
-
-   The driver computes from the desired period which clock divider it
-should be using. This computation assumes that the link between the
-register value and the actual divider value is raising 2 to the power of
-the registry value.
-
-    div = 1 << regvalue
-
-   This is true only for the first 5 values out of 8. Next values are
-64, 256 and, 1024.
-   This affects only the user only if he requests a period > 0.04369s.
-   I solved this by replacing the computation of the divider value with
-a lookup table.
-
-   If I should provide it in a different manner for it to be included in
-the kernel, please let me know.
-
-Best regards
-
-Gaetan Hug
-
-------
-
-Index: linux-3.18.5/drivers/pwm/pwm-mxs.c
-===================================================================
---- linux-3.18.5.orig/drivers/pwm/pwm-mxs.c	2015-01-30 02:41:03.000000000 +0100
-+++ linux-3.18.5/drivers/pwm/pwm-mxs.c	2015-02-17 17:14:54.082954410 +0100
-@@ -51,16 +51,17 @@
-	unsigned int period_cycles, duty_cycles;
-	unsigned long rate;
-	unsigned long long c;
-+	unsigned const int cdiv[PERIOD_CDIV_MAX] = {1, 2, 4, 8, 16, 64, 256, 1024};
-
-	rate = clk_get_rate(mxs->clk);
-	while (1) {
--		c = rate / (1 << div);
-+		c = rate / cdiv[div];
-		c = c * period_ns;
-		do_div(c, 1000000000);
-		if (c < PERIOD_PERIOD_MAX)
-			break;
-		div++;
--		if (div > PERIOD_CDIV_MAX)
-+		if (div >= PERIOD_CDIV_MAX)
-			return -EINVAL;
-	}


hooks/post-receive
-- 
armadeus