From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 5CC031FECC7; Mon, 3 Feb 2025 09:59:45 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.19 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1738576786; cv=none; b=cFDq36gxM+U5gx7qOguzuP2NNn3rA3nYBzNWwU7S+cggy4kFeZORYqGeZUnggN6WHFO7WX+w99Hv/BUUMw/ISAOwQ0pyqytyS7eM7hZYZVuF51ompfs0jwYFzGeNotXQ+cPplJvT24to9NIjChd3nmq/luximXlCqjzB8iP+JHw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1738576786; c=relaxed/simple; bh=UTPLAEKXScseRBtEXKrj5Nggli2sCNdySDjyM++GK88=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=vEsCllynUK2DttPCKW4Vk1cPdXUGJ/3vPkioVjPR6SNn/PN381gbT3k8f2kXTIQipIx+WNJCWb+CNkzfySCF7TqF0X9hNPqg6OoJ5+ohggsrcOpvw084ThiS5hSIcTH2Td4daDqQJ1vNlbpli8gZ9uHCT19f4K+TGcOhLR47IrA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com; spf=none smtp.mailfrom=linux.intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=bzIv+Vdx; arc=none smtp.client-ip=192.198.163.19 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="bzIv+Vdx" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1738576785; x=1770112785; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=UTPLAEKXScseRBtEXKrj5Nggli2sCNdySDjyM++GK88=; b=bzIv+VdxjlfUJTprKkxKUdAdxgS5MEHsBFvR7/biEvVVbAWiXnFH5KpY 03BHciRoaTjAesQk8Vg39hSOqDIABE64JbN2Yk2ctkT2q7DVyM2ylD30F dvx0gNvlLSg2sFu7Hv/tByQj9/IL/BrpoMNNV8Jxxsbjw2rIOdZ74KA9w g1bnbLj+Pq3nNel6uu9isKd4yEU25LWb64TVyc/h5KMJUmsrVpInUUBWq CtPxWZWwBeeBf6iWIA0x3HgP6qy4cTik4GbdUJT4obolRYEX5DpOi/cvl KH5MHMPIjgUkrc5Vzu+tbEiC/APEr44D3mvn5PagNUwbfp48mEYbpKq6o g==; X-CSE-ConnectionGUID: 1bP9lNJOQo+EPaYjvSGiWA== X-CSE-MsgGUID: oCMhNdxNSH28rN2pj0lH+Q== X-IronPort-AV: E=McAfee;i="6700,10204,11334"; a="38268655" X-IronPort-AV: E=Sophos;i="6.13,255,1732608000"; d="scan'208";a="38268655" Received: from orviesa008.jf.intel.com ([10.64.159.148]) by fmvoesa113.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Feb 2025 01:59:44 -0800 X-CSE-ConnectionGUID: 4CfyXycCRhiNlVGDA1PMww== X-CSE-MsgGUID: 2SL5EZe/RqCVPQYmnsc8tw== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.12,224,1728975600"; d="scan'208";a="111097864" Received: from smile.fi.intel.com ([10.237.72.58]) by orviesa008.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Feb 2025 01:59:43 -0800 Received: from andy by smile.fi.intel.com with local (Exim 4.98) (envelope-from ) id 1tetEy-00000007n8R-0SyS; Mon, 03 Feb 2025 11:59:40 +0200 Date: Mon, 3 Feb 2025 11:59:39 +0200 From: Andy Shevchenko To: Mika Westerberg Cc: Hans de Goede , linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org, Linus Walleij Subject: Re: [PATCH v1 0/2] pinctrl: intel: Unify the way of handling chained IRQ Message-ID: References: <20250129145155.1746876-1-andriy.shevchenko@linux.intel.com> <20250130124743.GX3713119@black.fi.intel.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20250130124743.GX3713119@black.fi.intel.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo On Thu, Jan 30, 2025 at 02:47:43PM +0200, Mika Westerberg wrote: > On Wed, Jan 29, 2025 at 04:49:38PM +0200, Andy Shevchenko wrote: > > Some of the drivers are using the dedicated helpers (chained_irq_enter(), > > chained_irq_exit() helpers) and some relies on the specific implementations > > of the parent IRQ chip and its configuration. Update the latter ones to > > use dedicated helpers that cover all possible scenarios. > > > > Andy Shevchenko (2): > > pinctrl: baytrail: Use dedicated helpers for chained IRQ handlers > > pinctrl: lynxpoint: Use dedicated helpers for chained IRQ handlers > > Both, > > Acked-by: Mika Westerberg Pushed to my review and testing queue, thanks! -- With Best Regards, Andy Shevchenko