Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754490AbcDSNnO (ORCPT ); Tue, 19 Apr 2016 09:43:14 -0400 Received: from mail-wm0-f46.google.com ([74.125.82.46]:38629 "EHLO mail-wm0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752407AbcDSNnM (ORCPT ); Tue, 19 Apr 2016 09:43:12 -0400 MIME-Version: 1.0 In-Reply-To: <57163252.5090000@schinagl.nl> References: <1461051650-18824-1-git-send-email-oliver@schinagl.nl> <5715F927.3030102@samsung.com> <5715FCE8.7080106@schinagl.nl> <57163252.5090000@schinagl.nl> From: Ricardo Ribalda Delgado Date: Tue, 19 Apr 2016 15:42:51 +0200 Message-ID: Subject: Re: [PATCHv1 0/6] leds: pca9653x: support inverted outputs and cleanups To: Olliver Schinagl Cc: Jacek Anaszewski , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Richard Purdie , "devicetree@vger.kernel.org" , LKML , Linux LED Subsystem , Peter Meerwald Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 798 Lines: 23 Hi again On Tue, Apr 19, 2016 at 3:27 PM, Olliver Schinagl wrote: > Hey Ricardo, > Without actually looking at the code right now, but the driver does a > read/modify/write on the register, and a register is shared among several > leds. So in that regard, it makes sense and I don't think it's very > expensive to move the lock, since we have to lock for the write a few lines > down anyway. Actually, the code is only making sure that PCA963X_MODE2_DMBLNK is on. It is never cleared afterwards. It will be great if you could set that bit on probe and remove those two lines and verify that it works on real hardware. The move of the lock can be a bit expensive. i2c writes can take a while to be performed, this is why only ledout was protected initially. Best regards