Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp646932imu; Thu, 3 Jan 2019 04:44:24 -0800 (PST) X-Google-Smtp-Source: AFSGD/Wxq01D80IptkhPYdg62NID4m8SMyqovO3xlEopJ/lR00BuKhno8cIiI6EhTS0VjRYQHXFu X-Received: by 2002:a62:109b:: with SMTP id 27mr47178054pfq.227.1546519464549; Thu, 03 Jan 2019 04:44:24 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1546519464; cv=none; d=google.com; s=arc-20160816; b=WZY7DtH1b9U/6ovnxZksSCkmO5k6xjVIuMP53DVbGaE5R8s0FT8AYHIvivLxohWbrb a5fJ182+UdqRj2DSfZfE0pVx7uaDRec3UynBwkSM5dJFwKMMJ9QCOE4o5gutB3QxATCZ EnWPYsMAYWwtP7dsF9kal9Shn1jA/r963bR5eEr9nWSgH52rysXlMyqKh4qcb/OI1+qT yFBVDSqN9t3iojmsd0buWGt0O1gdhK1g2aVI0hr/SyuuAKaNDDTAuV8UewcqKyR00g8b 3ep8JHqPukjMTymRYedjTDLj1cAx2MqVKzsWw+TQpnRExy0UlMFVaRFiltpqvJgi9MMY Gtsg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=rI9/8JqBwCPRGXE3VQuLgj1e3ciVM4ELhZVJD1qC6rQ=; b=n/Z3UkHU66TJKLDh3xEVeeZ95VDB3mg/Z+TmFPW2aI1yCnsZ0kCuIQCkEoz0UqjVSW ZvFuLZIsbX3EwBFDtbhGwl1gLoUkEHcfME1Uw2is5OFVfeIWDGSnskaIsbvKdXGK1MFg /h/ypm0VHqadg+XGXhijhAEdaWRlRsqb+zxAS+wCBBppxYj8OqUytXcaYWZ3kIkn71wh 2hDdkvgIgAn6QD3qfR5Av9F6TuPJTk4T4/aI6y96YwwyorpVSd6UXsVwINw15u/BIV2u Ht2n7CmG42xVNjxRP1c4GcjFbuaeYCXAPGePREcniH8+MINoRoZOLa+LcMvYPCiXFcXz l6IA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d8si30272711pgl.386.2019.01.03.04.44.05; Thu, 03 Jan 2019 04:44:24 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730471AbfACJaV (ORCPT + 99 others); Thu, 3 Jan 2019 04:30:21 -0500 Received: from mga09.intel.com ([134.134.136.24]:7737 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726152AbfACJaU (ORCPT ); Thu, 3 Jan 2019 04:30:20 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga007.jf.intel.com ([10.7.209.58]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Jan 2019 01:30:19 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,434,1539673200"; d="scan'208";a="103594391" Received: from rfried-ivm1.ger.corp.intel.com (HELO [10.185.130.184]) ([10.185.130.184]) by orsmga007.jf.intel.com with ESMTP; 03 Jan 2019 01:30:17 -0800 Subject: Re: RFC: gpio: mmio: add support for 3 direction regs To: Vladimir Zapolskiy , linus.walleij@linaro.org, bgolaszewski@baylibre.com, linux-gpio@vger.kernel.org Cc: linux-kernel@vger.kernel.org, vladimir.kondratiev@linux.intel.com References: <32edfd70-95dc-26a1-2ea6-143344cb2384@linux.intel.com> <28205214-d395-1c17-51ee-970300b6a14e@linux.intel.com> <6f609cb3-b294-0e66-a68f-73ad7ee4ac9a@mentor.com> From: "Fried, Ramon" Message-ID: <8ead668a-2a1a-916a-585b-ac9830fdf490@linux.intel.com> Date: Thu, 3 Jan 2019 11:30:16 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.3 MIME-Version: 1.0 In-Reply-To: <6f609cb3-b294-0e66-a68f-73ad7ee4ac9a@mentor.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 1/3/2019 10:59, Vladimir Zapolskiy wrote: > On 01/03/2019 10:51 AM, Fried, Ramon wrote: >> On 1/3/2019 10:07, Vladimir Zapolskiy wrote: >>> Hi Ramon, >>> >>> On 01/03/2019 09:36 AM, Fried, Ramon wrote: >>>> Hi. >>>> >>>> I'm working on a driver for STA2X11 GPIO controller who seems to fit >>>> best to the generic mmio driver, >>> I hope you have seen the existing driver drivers/gpio/gpio-sta2x11.c >> I surely did. we have the same IP in our soc but it was changed a lot >> internally, don't want to litter the original. >>>> the only problem I have is with the dir register case. The STA2X11 >>>> has 3 registers for dir, one for data, one for set and one for >>>> clear. The generic-mmio driver has support for this fashion for the >>>> dat & set & clear registers but not for dirout/dirin registers. >>>> >>>> I wonder if support for this is generic enough to deserve a patch, if >>>> so I'm willing to quickly add this support, if not, adding a flag >>>> such as below, will allow partly using the generic mmio driver only >>>> for set/get and the direction can be handled outside the driver. >>>> >>> If gpio-mmio fits well, then it might be simpler to set a flag >>> BGPIOF_UNREADABLE_REG_DIR, then call bgpio_init() and then overwrite >>> .direction_input, .direction_output and .get_direction callbacks, >>> as a reference you can take a look at gpio-74xx-mmio.c >> Nice. >> That's an option I didn't think of, better than setting the flag. >> what about adding the generic support ? > Setting a GPIO direction over three different registers doesn't sound > as a suitable candidate for generalization, also your particular > implementation is partial, relies on external platform/driver code > to preset the directions and it does not allow to change direction > in runtime, so just renounce the idea. Alrighty then, will overwrite the direction CBs. Thanks. > > -- > Best wishes, > Vladimir