From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754029AbaHKPWX (ORCPT ); Mon, 11 Aug 2014 11:22:23 -0400 Received: from arroyo.ext.ti.com ([192.94.94.40]:53122 "EHLO arroyo.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753465AbaHKPWV (ORCPT ); Mon, 11 Aug 2014 11:22:21 -0400 Message-ID: <53E8EA15.2040003@ti.com> Date: Mon, 11 Aug 2014 19:06:45 +0300 From: Grygorii Strashko User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Linus Walleij CC: Santosh Shilimkar , Alexandre Courbot , "linux-gpio@vger.kernel.org" , ivan.khoronzhuk@ti.com, Muralidharan Karicheri , Rob Herring , Kumar Gala , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Varka Bhadram Subject: Re: [PATCH v2] gpio: keystone: add dsp gpio controller driver References: <1406126699-10053-1-git-send-email-grygorii.strashko@ti.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Linus, On 08/08/2014 03:53 PM, Linus Walleij wrote: > On Wed, Jul 23, 2014 at 4:44 PM, Grygorii Strashko > wrote: > >> From: Murali Karicheri >> >> On Keystone SOCs, ARM host can send interrupts to DSP cores using the >> DSP GPIO controller IP. Each DSP GPIO controller provides 28 IRQ signals for >> each DSP core. This is one of the component used by the IPC mechanism used >> on Keystone SOCs. >> >> Keystone 2 DSP GPIO controller has specific features: >> - each GPIO can be configured only as output pin; >> - setting GPIO value to 1 causes IRQ generation on target DSP core; >> - reading pin value returns 0 - if IRQ was handled or 1 - IRQ is still >> pending. >> >> Signed-off-by: Murali Karicheri >> Signed-off-by: Grygorii Strashko >> --- >> Changes in v2: >> - minor comments applied > > Hm so there was one major comment, quoting myself: > > "And if you proceed with this, please integrate it with > drivers/gpio/gpio-syscon.c, I don't need more special > syscons GPIO handlers." > > Maybe you missed this in the midst of the other discussions > about whether this is GPIO at all, but that comment still > stands even if you talk me down on the generality of this > driver. > There is some misunderstanding, sorry. And I've not missed your Major comment. I posted v2 after a week after v1, but, unfortunately, right before discussion on v1 had been actually started :( >> +++ b/Documentation/devicetree/bindings/gpio/gpio-keystone.txt > > Make this follow the style in: > Documentation/devicetree/bindings/gpio/cirrus,clps711x-mctrl-gpio.txt > Regards, -grygorii