Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp99481iob; Thu, 12 May 2022 19:44:24 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzd+jSFZGkcs4nOf/uo+x5Sk1lKjVL76eJ0kT7daeiLaiZZAfrgayv8RsBW/rnJwfj8R5Jw X-Received: by 2002:a17:906:4fc4:b0:6da:b4c6:fadb with SMTP id i4-20020a1709064fc400b006dab4c6fadbmr2435819ejw.282.1652409864299; Thu, 12 May 2022 19:44:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1652409864; cv=none; d=google.com; s=arc-20160816; b=RzCvm1FuOqDhoa2pz909Vam5RsF5plZ+voEr5p2xck7je+iA5akMG9yyex9WClLWPx NaV95VAK7YWqQYq5uZX8yc66SU3lDMqq/gXe4P0X34vEvsPv2BTTQUYiHci8Ld2pfaFV Wnqq/3R2FxaJZLKsAKNSfDqDMcKjRH9MD+sL8PTP09xHnjOR79OkRHVNacMn3kEipeaV TPsFmY1rDlNzWYUBXtfKOOJjA+K6NNgrjmdDhkB7FynwUJ4GzYBrWrNuKTpVsBv1K0Ec NsIQNJo/5PpnDH2BVbuWWTMB1oSMIBgdwZwEfWKCLjKnrzmDPeIx0ex/iYeL/GiL5uP5 n6pQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=HJgOTr7AmV20I4ZQHCjOvGH1oUoi3a/3HcI1evx8nvE=; b=STApsD1+0WNI/eFSDyuguBgbaklAsiGQSKySf0Od1d9ME7hHHaLHkIPWsGpMj2kLoj h9chSaAQX5w/oXYWro+SoCH8Z1Cr/h1jbnlBXIt2NYB+kmwIUOaGxbkOygMrEKokeGbE cObyeb5yso8WsbsvSWQeRCGvB94ur7UjQPlaNtwR5V81XGbTflu0YyQYPtT/ogiIIXgd Zksz/zvyQhyk7Lv8S/+CjUWCHnodEs34ojJZRooz70uNECWm32wBQn/ltAbQj9D9junL uDD49RudpA/FQsCGHjFZaIqdfhxxQxQ3g5+hENRUxLGoJBp3tMU7/EAHE7lHujrVaS29 kjNw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=BIk7ms8i; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id e14-20020a056402330e00b00425b9256be6si826012eda.117.2022.05.12.19.43.59; Thu, 12 May 2022 19:44:24 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=BIk7ms8i; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1357134AbiELRjl (ORCPT + 99 others); Thu, 12 May 2022 13:39:41 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40696 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1355439AbiELRji (ORCPT ); Thu, 12 May 2022 13:39:38 -0400 Received: from mga06.intel.com (mga06b.intel.com [134.134.136.31]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 398C6267096; Thu, 12 May 2022 10:39:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1652377177; x=1683913177; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=57zZUQo2XpYyqv/Fq0Q307fjDwWri2ChI3FAS8rHfMs=; b=BIk7ms8iFTjQbBOZm40PjyGlMEmeSHzMZcEWwi2mGIjOhoTXxBeTeNGH LBNJ45zWVBOU1kFs9zE2yNnwDe9sON8/Sg4hFBmfKprcWIHjo0Uq4BFTc X4cCv6xonVfvjvkvOYOKBm2Q7Mlr0T2ea+qgc1LO7KX2MXWU404zGMOyt yEECKrUH6lDbGjoLiGWy4t/S9eu3vWA7ZVoGhTmJBF6BPRirXDqGtI/4+ KONCCoN5EJMz0yM7hPdufBgalhNoAb9j6/9UjLxaDHx00GxOJqleZAsou UiGMZiMaz6ubMC0yq8mfgRptTVEaqBhA6Mn1EXuWBpY0KCdnWhxZUffJa g==; X-IronPort-AV: E=McAfee;i="6400,9594,10345"; a="330691118" X-IronPort-AV: E=Sophos;i="5.91,220,1647327600"; d="scan'208";a="330691118" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 12 May 2022 10:39:36 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.91,220,1647327600"; d="scan'208";a="594787760" Received: from black.fi.intel.com ([10.237.72.28]) by orsmga008.jf.intel.com with ESMTP; 12 May 2022 10:39:33 -0700 Received: by black.fi.intel.com (Postfix, from userid 1003) id 378A9CE; Thu, 12 May 2022 20:39:32 +0300 (EEST) From: Andy Shevchenko To: Andy Shevchenko , Marc Zyngier , Hans de Goede , linux-gpio@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Linus Walleij , Bartosz Golaszewski , Jonathan Corbet , Mika Westerberg , Andy Shevchenko Subject: [PATCH v1 1/5] Documentation: gpio: Fix IRQ mask and unmask examples Date: Thu, 12 May 2022 20:39:17 +0300 Message-Id: <20220512173921.8210-1-andriy.shevchenko@linux.intel.com> X-Mailer: git-send-email 2.35.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-4.9 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org After switching to immutable IRQ chips for GPIO drivers the examples become uncompilable due to wrong IRQ API, i.e. irq_desc_get_handler_data() in use. Replace it with proper irq_data_get_irq_chip_data() call where it applies. Fixes: 5644b66a9c63 ("Documentation: Update the recommended pattern for GPIO irqchips") Signed-off-by: Andy Shevchenko --- Documentation/driver-api/gpio/driver.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/Documentation/driver-api/gpio/driver.rst b/Documentation/driver-api/gpio/driver.rst index a1ddefa1f55f..964d09118d17 100644 --- a/Documentation/driver-api/gpio/driver.rst +++ b/Documentation/driver-api/gpio/driver.rst @@ -429,7 +429,7 @@ call into the core gpiolib code: static void my_gpio_mask_irq(struct irq_data *d) { - struct gpio_chip *gc = irq_desc_get_handler_data(d); + struct gpio_chip *gc = irq_data_get_irq_chip_data(d); /* * Perform any necessary action to mask the interrupt, @@ -442,7 +442,7 @@ call into the core gpiolib code: static void my_gpio_unmask_irq(struct irq_data *d) { - struct gpio_chip *gc = irq_desc_get_handler_data(d); + struct gpio_chip *gc = irq_data_get_irq_chip_data(d); gpiochip_enable_irq(gc, d->hwirq); @@ -501,7 +501,7 @@ the interrupt separately and go with it: static void my_gpio_mask_irq(struct irq_data *d) { - struct gpio_chip *gc = irq_desc_get_handler_data(d); + struct gpio_chip *gc = irq_data_get_irq_chip_data(d); /* * Perform any necessary action to mask the interrupt, @@ -514,7 +514,7 @@ the interrupt separately and go with it: static void my_gpio_unmask_irq(struct irq_data *d) { - struct gpio_chip *gc = irq_desc_get_handler_data(d); + struct gpio_chip *gc = irq_data_get_irq_chip_data(d); gpiochip_enable_irq(gc, d->hwirq); @@ -576,7 +576,7 @@ In this case the typical set-up will look like this: static void my_gpio_mask_irq(struct irq_data *d) { - struct gpio_chip *gc = irq_desc_get_handler_data(d); + struct gpio_chip *gc = irq_data_get_irq_chip_data(d); /* * Perform any necessary action to mask the interrupt, @@ -590,7 +590,7 @@ In this case the typical set-up will look like this: static void my_gpio_unmask_irq(struct irq_data *d) { - struct gpio_chip *gc = irq_desc_get_handler_data(d); + struct gpio_chip *gc = irq_data_get_irq_chip_data(d); gpiochip_enable_irq(gc, d->hwirq); -- 2.35.1