Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752637AbaGLXvu (ORCPT ); Sat, 12 Jul 2014 19:51:50 -0400 Received: from mail-oa0-f46.google.com ([209.85.219.46]:37560 "EHLO mail-oa0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751020AbaGLXvs (ORCPT ); Sat, 12 Jul 2014 19:51:48 -0400 MIME-Version: 1.0 In-Reply-To: <1404999558.16296.31.camel@iivanov-dev> References: <1404745893-6379-1-git-send-email-iivanov@mm-sol.com> <1404904380.16296.17.camel@iivanov-dev> <1404999558.16296.31.camel@iivanov-dev> Date: Sat, 12 Jul 2014 16:51:47 -0700 Message-ID: Subject: Re: [PATCH 0/4] New Qualcomm PMIC pin controller drivers From: Bjorn Andersson To: "Ivan T. Ivanov" Cc: Linus Walleij , Bjorn Andersson , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Russell King , Grant Likely , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-arm-msm@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 10, 2014 at 6:39 AM, Ivan T. Ivanov wrote: > On Wed, 2014-07-09 at 07:02 -0700, Bjorn Andersson wrote: [..] >> Correct Ivan; we do however share the same issues related to how to do >> interrupt handling, > > Yep, but do we actually need to do interrupt handling in driver? > Interrupts are handled by parent device. GPIO client drivers could > use interrupt-controller registered by core driver? > Among other things we have the volume and camera keys hooked to these pins, using the gpio-keys driver; so that needs to be able to convert a gpio to an irq. But I don't believe we should turn this driver into an interrupt-controller; as that wouldn't add any value... Regards, Bjorn -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/