Date: Thu, 10 May 2012 14:40:16 -0700
From: Andrew Morton <akpm@linux-foundation.org>
To: Alexander Stein <alexander.stein@systec-electronic.com>
Cc: Richard Purdie <rpurdie@rpsys.net>, linux-kernel@vger.kernel.org,
        Bryan Wu <bryan.wu@canonical.com>
Subject: Re: [PATCH] leds-pca955x: Fix race condition while setting
 brightness on several LEDs
Message-Id: <20120510144016.3a1b006c.akpm@linux-foundation.org>
In-Reply-To: <1328705048-21073-1-git-send-email-alexander.stein@systec-electronic.com>
References: <1328705048-21073-1-git-send-email-alexander.stein@systec-electronic.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1198
Lines: 33

On Wed,  8 Feb 2012 13:44:08 +0100
Alexander Stein <alexander.stein@systec-electronic.com> wrote:

> When issuing the following command:
> for I in 0 1 2 3 4 5 6 7; do
>   echo 0 > /sys/class/leds/pca955x\:${I}/brightness;
> done
> It is possible that all the pca955x_read_ls calls are done sequentially
> before any pca955x_write_ls call is done. This updates the LS only to the
> last LED update in its set.
> Fix this by using a global lock for the pca995x device during
> pca955x_led_work.

There's the bugfix.

> Also used a struct for shared data bewteen all LEDs.

And there's an apparently unrelated change whcih created a *lot* of
noise in the patch.  It would be good to separate these things, with
the bugfix being the first change.

> ...
>
> -static inline u8 pca955x_ledsel(u8 oldval, int led_num, int state)
> +static inline u8 pca955x_ledel(u8 oldval, int led_num, int state)

Why was this function renamed, and what does "ledel" mean?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/