From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753272AbcBVTmw (ORCPT ); Mon, 22 Feb 2016 14:42:52 -0500 Received: from 5520-maca-inet1-outside.broadcom.com ([216.31.211.11]:21135 "EHLO mail-irv-18.broadcom.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751236AbcBVTmu (ORCPT ); Mon, 22 Feb 2016 14:42:50 -0500 Subject: Re: [PATCH v2 1/3] input: cygnus-update touchscreen dt node document To: Dmitry Torokhov , Raveendra Padasalagi References: <1455702226-20599-1-git-send-email-raveendra.padasalagi@broadcom.com> <1455702226-20599-2-git-send-email-raveendra.padasalagi@broadcom.com> <20160218143617.GH9654@rob-hp-laptop> <20160222193604.GA26177@dtor-ws> Cc: Rob Herring , Russell King , Arnd Bergmann , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-input@vger.kernel.org, Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Jonathan Richardson , Jon Mason , Florian Fainelli , Anup Patel , Ray Jui , Scott Branden , linux-kernel@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com From: Scott Branden Message-ID: <56CB6471.3020400@broadcom.com> Date: Mon, 22 Feb 2016 11:41:37 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: <20160222193604.GA26177@dtor-ws> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org My comments below On 16-02-22 11:36 AM, Dmitry Torokhov wrote: > On Fri, Feb 19, 2016 at 11:43:50AM +0530, Raveendra Padasalagi wrote: >> On Thu, Feb 18, 2016 at 8:06 PM, Rob Herring wrote: >>> On Wed, Feb 17, 2016 at 03:13:44PM +0530, Raveendra Padasalagi wrote: >>>> In Cygnus SOC touch screen controller registers are shared >>>> with ADC and flex timer. Using readl/writel could lead to >>>> race condition. So touch screen driver is enhanced to support >>>> >>>> 1. If touchscreen register's are not shared. Register access >>>> is handled through readl/writel if "brcm,iproc-touchscreen" >>>> compatible is provided in touchscreen dt node. This will help >>>> for future SOC's if comes with dedicated touchscreen IP register's. >>>> >>>> 2. If touchscreen register's are shared with other IP's, register >>>> access is handled through syscon framework API's to take care of >>>> mutually exclusive access. This feature can be enabled by selecting >>>> "brcm,iproc-touchscreen-syscon" compatible string in the touchscreen >>>> dt node. >>>> >>>> Hence touchscreen dt node bindings document is updated to take care >>>> of above changes in the touchscreen driver. >>>> >>>> Signed-off-by: Raveendra Padasalagi >>>> Reviewed-by: Ray Jui >>>> Reviewed-by: Scott Branden >>>> --- >>>> .../input/touchscreen/brcm,iproc-touchscreen.txt | 57 +++++++++++++++++++--- >>>> 1 file changed, 51 insertions(+), 6 deletions(-) >>>> >>>> diff --git a/Documentation/devicetree/bindings/input/touchscreen/brcm,iproc-touchscreen.txt b/Documentation/devicetree/bindings/input/touchscreen/brcm,iproc-touchscreen.txt >>>> index 34e3382..f530c25 100644 >>>> --- a/Documentation/devicetree/bindings/input/touchscreen/brcm,iproc-touchscreen.txt >>>> +++ b/Documentation/devicetree/bindings/input/touchscreen/brcm,iproc-touchscreen.txt >>>> @@ -1,12 +1,30 @@ >>>> * Broadcom's IPROC Touchscreen Controller >>>> >>>> Required properties: >>>> -- compatible: must be "brcm,iproc-touchscreen" >>>> -- reg: physical base address of the controller and length of memory mapped >>>> - region. >>>> +- compatible: should be one of >>>> + "brcm,iproc-touchscreen" >>>> + "brcm,iproc-touchscreen-syscon" >>> >>> More specific and this is not how you do syscon. Either the block is or >>> isn't. You can't have it both ways. >> >> Existing driver has support for reg, if we modify now to support only syscon >> then this driver will not work if some one wishes to use previous >> kernel version's >> dt and vice versa. Basically this breaks dt compatibility. Is that ok ? > > But the issue is that the driver does not actually work correctly with > direct register access on those systems, since the registers are > actually shared with other components. I am not quite sure if it is OK > to break DT binding in this case... The driver does work correctly with direct register access on those systems because the other components using those registers are not active in those systems - so syscon is not needed in those cases. I'm ok with not containing backwards compatibility though and always using syscon. There are no deployed systems using older versions of the upstreamed kernel. > > Thanks. > Regards, Scott