From patchwork Wed Oct 9 16:46:13 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Andy Shevchenko X-Patchwork-Id: 1173870 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Authentication-Results: ozlabs.org; spf=none (mailfrom) smtp.mailfrom=vger.kernel.org (client-ip=209.132.180.67; helo=vger.kernel.org; envelope-from=linux-gpio-owner@vger.kernel.org; receiver=) Authentication-Results: ozlabs.org; dmarc=none (p=none dis=none) header.from=linux.intel.com Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 46pKqL2lLyz9s7T for ; Thu, 10 Oct 2019 03:46:22 +1100 (AEDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731145AbfJIQqV (ORCPT ); Wed, 9 Oct 2019 12:46:21 -0400 Received: from mga06.intel.com ([134.134.136.31]:9910 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731083AbfJIQqU (ORCPT ); Wed, 9 Oct 2019 12:46:20 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Oct 2019 09:46:20 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.67,276,1566889200"; d="scan'208";a="200185146" Received: from black.fi.intel.com ([10.237.72.28]) by FMSMGA003.fm.intel.com with ESMTP; 09 Oct 2019 09:46:19 -0700 Received: by black.fi.intel.com (Postfix, from userid 1003) id 6C58016A; Wed, 9 Oct 2019 19:46:18 +0300 (EEST) From: Andy Shevchenko To: andy.shevchenko@gmail.com, Linux GPIO Subject: [GIT PULL] intel-gpio for 5.4-2 Date: Wed, 9 Oct 2019 19:46:13 +0300 Message-Id: <20191009164618.76442-1-andriy.shevchenko@linux.intel.com> X-Mailer: git-send-email 2.23.0 MIME-Version: 1.0 Sender: linux-gpio-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org Hi Linux GPIO maintainers, Small set of urgent fixes against Intel GPIO drivers that have been recently converted to use GPIO core for instantiation of IRQ chip. No conflicts observed with fixes branch of GPIO tree as of today. Thanks, With Best Regards, Andy Shevchenko The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c: Linux 5.4-rc1 (2019-09-30 10:35:40 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/andy/linux-gpio-intel.git tags/intel-gpio-v5.4-2 for you to fetch changes up to 6ed26a5326f6da6e1950b8476173df51a92a96be: gpio: lynxpoint: set default handler to be handle_bad_irq() (2019-10-09 19:00:13 +0300) ---------------------------------------------------------------- intel-gpio for v5.4-2 The conversion to use of GPIO core to instantiate IRQ chip produced several issues among the drivers. Here is the set of fixes to: * initialize hardware before IRQ chip will be added * initialize hardware without NULL pointer dereference * assign IRQ base The following is an automated git shortlog grouped by driver: gpiolib: - Initialize the hardware with a callback intel-mid: - Move hardware initialization to callback lynxpoint: - set default handler to be handle_bad_irq() - Move hardware initialization to callback merrifield: - Move hardware initialization to callback - Restore use of irq_base ---------------------------------------------------------------- Andy Shevchenko (6): gpio: merrifield: Restore use of irq_base gpiolib: Initialize the hardware with a callback gpio: intel-mid: Move hardware initialization to callback gpio: lynxpoint: Move hardware initialization to callback gpio: merrifield: Move hardware initialization to callback gpio: lynxpoint: set default handler to be handle_bad_irq() drivers/gpio/gpio-intel-mid.c | 9 ++++++--- drivers/gpio/gpio-lynxpoint.c | 10 ++++++---- drivers/gpio/gpio-merrifield.c | 9 ++++++--- drivers/gpio/gpiolib.c | 22 +++++++++++++++++++++- include/linux/gpio/driver.h | 8 ++++++++ 5 files changed, 47 insertions(+), 11 deletions(-)