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;
Subject: Re: [PATCH 2/2] gpio: sch: Add interrupt support
To:     Mika Westerberg <mika.westerberg@linux.intel.com>
Cc:     Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
        Linus Walleij <linus.walleij@linaro.org>,
        Bartosz Golaszewski <bgolaszewski@baylibre.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org,
        "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
References: <20190424075816.GU2654@lahna.fi.intel.com>
 <8999d3f8-d169-eb85-bd2f-08c99d184ea2@siemens.com>
 <20190424081802.GV2654@lahna.fi.intel.com>
 <5a28f22c-22f7-760a-d076-68ff19800d44@siemens.com>
 <20190424084259.GW2654@lahna.fi.intel.com>
 <7e328b7e-f4f0-851a-4152-a9ffd058201c@siemens.com>
 <20190424094506.GA2654@lahna.fi.intel.com>
 <292e6eff-82cc-6e4d-925b-77a60399e2e0@siemens.com>
 <20190424100130.GB2654@lahna.fi.intel.com>
 <1200464b-f969-ebc2-ae82-1f8ca98aaca1@siemens.com>
 <20190424103306.GC2654@lahna.fi.intel.com>
From:   Jan Kiszka <jan.kiszka@siemens.com>
Message-ID: <9377620b-d74a-04d9-a51e-8590400b1c0f@siemens.com>
Date:   Wed, 24 Apr 2019 12:39:35 +0200
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12)
 Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666
MIME-Version: 1.0
In-Reply-To: <20190424103306.GC2654@lahna.fi.intel.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On 24.04.19 12:33, Mika Westerberg wrote:
> On Wed, Apr 24, 2019 at 12:19:02PM +0200, Jan Kiszka wrote:
>>> I think what you want is "GPIO signaled ACPI event". It works so that
>>> you declare _AEI method below the GPIO controller listing the GPIOs you
>>> want to trigger events for and then either _Lxx, _Exx or _EVT method for
>>> each of them under the same controller. GPIO core then handles it
>>> automatically when you register the GPIO chip. See also
>>> acpi_gpiochip_request_interrupts().
>>
>> Right, that is was I read as well. Let's assume I would be able to patch the
>> tables: Would I describe all the logic of this patch in ACPI terms? Where to
>> enable interrupts, how to dispatch the SCI event, how to acknowledge it
>> etc.? Will it also take care of locking? (BTW, my locking seems to have some
>> remaining inconsistency, on second look.)
> 
> The GPIO core would then take care of it by requesting the GPIO in
> question and dispatching to the correct event handler. In this patch you
> just leave out the SCI part and only implement the irqchip like you did
> already.

Could you point me to a gpio driver that works like that already? Would be 
easier to learn that from an example. That infrastructure with all its different 
modes is seriously complex and not very well documented.

> 
>> And even if that were possible, we would be back to the square of existing
>> devices without those definitions. If this were a recent chipset, I would
>> say, "go, fix future firmware versions". But this one is legacy.
> 
> Is it fixing some real issue with these legacy platforms? I mean without
> the patch some GPE event is not handled properly? It was not clear to me
> from the commit message.
> 

Without that patch, you are forced to poll for event changes in your 
application, timer-driven. There are application that cannot process these GPIOs 
because they lack such logic (mraa with node-red-node-intel-gpio is a public 
example).

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux