Received: by 2002:a05:6a10:413:0:0:0:0 with SMTP id 19csp758839pxp; Fri, 11 Mar 2022 14:21:36 -0800 (PST) X-Google-Smtp-Source: ABdhPJzlzTA8JAaIDQ+iszerdggjprhUDOuPZveWZ2mx3xJeDv1R1l3mUG/dcK5/HnG7BzwQGMZT X-Received: by 2002:a65:4003:0:b0:37f:f658:8fd1 with SMTP id f3-20020a654003000000b0037ff6588fd1mr10193753pgp.214.1647037295928; Fri, 11 Mar 2022 14:21:35 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1647037295; cv=none; d=google.com; s=arc-20160816; b=C+oQAZYLomnDgrS7Ps4S/jl+gEGl6dZ1H7x8EN6iSn7OU9Cc3ix5Jtsq/+m5o62P29 EEXVP8F/toTNfrgRqeqnzgYOodEURoCxj/+IqJ67gsmLOZT6mJBmUynkT+yoB3GJYPlS M+inldwz35LGF/53bCeLWS4rh2Glg5mpYCBEnOCAF8aj5LXqDEpVIRzt0zqusWjXQgXj A73eoLr2JHs+8475Aqcz9o6whP7y8qBpM+7U+EPzsDhqbNn2FhNek+9r0A1IX1HmuEcB zDyIqpJ6oNU/SYRM5wV7ZCPrWUHU6mhAhmTdWSLsiTG2zB+WhKTrbz8r10HS03Tx3x9E hnSA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=yo5cNZOSv/J/WvklnDG16ry9Bw3elHchQ9q/vBCqvbQ=; b=igmWv1lnAueNHwnxK1t+8WYJt1x7UFYUFYQPsqxrYVMGFZB5Qqt2JRXID2RbpjIXTD a1y9forX0oi+SvkPbdCm4mWeNqHYPN791H4UNw8I8+148/ZNEOi83rmg/p1kJFXYWHpM Pod0VxWPiQv9ooPa1bMAvrD0Fx5RxW4VO6W1IMO6gLDAqS6F/janpSXex5GrOapk18b6 CdnNUlGTqcMZqiDEMjwaA+gCQxUTKBXNPdD9AvioR3i3ZMOJSyHAeZhCSIjJo88Z8JGn qEiyCu7rsO3lcexoGWZz/ccDLavIBTrgmgGX2EPGjqJp66G6MKJfXwU6iPLKc/PNUlGI O4ZQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=maGHS2m9; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [23.128.96.19]) by mx.google.com with ESMTPS id x191-20020a6386c8000000b0037c903304c2si8864321pgd.840.2022.03.11.14.21.35 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 11 Mar 2022 14:21:35 -0800 (PST) Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=maGHS2m9; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 565662E4080; Fri, 11 Mar 2022 13:30:23 -0800 (PST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243517AbiCJOW6 (ORCPT + 99 others); Thu, 10 Mar 2022 09:22:58 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40422 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S244237AbiCJOTD (ORCPT ); Thu, 10 Mar 2022 09:19:03 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B4CE816EAA5; Thu, 10 Mar 2022 06:15:48 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id D52D961C99; Thu, 10 Mar 2022 14:15:02 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 47E1CC340E8; Thu, 10 Mar 2022 14:15:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1646921702; bh=yo5cNZOSv/J/WvklnDG16ry9Bw3elHchQ9q/vBCqvbQ=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=maGHS2m9LDj84cxFFYKfEByaP+07rvv+owPqT7QN/rWpqfNcEJIgelSZsi89z4YEO eQ1qFs24G5TKKZ37vfsaWUuoahmWC2QwUDpYhUJOWTcA5ftlnYtglXuIm3C+NzvXVX gBXYfhzm3t7ZnwmCGQflz+r+w3644ExZdU582Wf+q3jK8KdwigqrOzzNj+ZaARW29C 7hn4UDgR975l1tpTzDFBwdz4PbSL/O4tpE2aHK4RWiwc0aMs1RoAbAgXX3XjuS86s3 HePHW4K+4ISCDz6AYjeZei8oxFadEePkK2O4JH54dDvQ9xfKcmwPJoy+iQaWP2GBHv 67tYi9URG2iMw== Received: by mail-ed1-f51.google.com with SMTP id w4so7136387edc.7; Thu, 10 Mar 2022 06:15:02 -0800 (PST) X-Gm-Message-State: AOAM533sFQ6Hbbpfbrv8YOLkfiPhbxZKL1SafpwCxR7e05ac5nwXrzTk mQQIcSGNUYNUX0PJA3TAFi6msy0GoFfApICOQg== X-Received: by 2002:a05:6402:5256:b0:416:97d1:a6a2 with SMTP id t22-20020a056402525600b0041697d1a6a2mr4571157edd.280.1646921700547; Thu, 10 Mar 2022 06:15:00 -0800 (PST) MIME-Version: 1.0 References: <20211224161334.31123-1-prabhakar.mahadev-lad.rj@bp.renesas.com> <20211224161334.31123-3-prabhakar.mahadev-lad.rj@bp.renesas.com> <5e13c1ba-0bf5-e360-c350-e7a1a1402350@linaro.org> In-Reply-To: <5e13c1ba-0bf5-e360-c350-e7a1a1402350@linaro.org> From: Rob Herring Date: Thu, 10 Mar 2022 08:14:48 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] slimbus: qcom-ngd-ctrl: Use platform_get_irq() to get the interrupt To: Srinivas Kandagatla Cc: "Lad, Prabhakar" , Lad Prabhakar , LKML , Andy Gross , Bjorn Andersson , linux-arm-msm , alsa-devel Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,MAILING_LIST_MULTI, RDNS_NONE,SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=unavailable 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 On Thu, Mar 10, 2022 at 4:42 AM Srinivas Kandagatla wrote: > > > > On 10/03/2022 10:23, Lad, Prabhakar wrote: > > On Thu, Mar 10, 2022 at 10:16 AM Srinivas Kandagatla > > wrote: > >> > >> > >> > >> On 24/12/2021 16:13, Lad Prabhakar wrote: > >>> platform_get_resource(pdev, IORESOURCE_IRQ, ..) relies on static > >>> allocation of IRQ resources in DT core code, this causes an issue > >> > >> Are you saying that we should not be using platform_get_resource(pdev, > >> IORESOURCE_IRQ, ...) on drivers that support DT? We should be using platform_get_irq(). (period, on all platform drivers) > >>> when using hierarchical interrupt domains using "interrupts" property > >>> in the node as this bypasses the hierarchical setup and messes up the > >>> irq chaining. > >> > >> Should this not be fixed in the DT core itself? > >> > > Yes the plan is to fix in the DT core itself (refer [0]). > > > > [0] https://patchwork.kernel.org/project/linux-renesas-soc/patch/20211209001056.29774-1-prabhakar.mahadev-lad.rj@bp.renesas.com/ > > > >>> > >>> In preparation for removal of static setup of IRQ resource from DT core > >>> code use platform_get_irq(). > >> > >> I would prefer this patch to be part of the series that removes IRQ > >> resource handling from DT core. > >> > > Since there are too many users (which are in different subsystems) > > getting this all in single series would be a pain. As a result it is > > split up into individual subsystems. > Am happy for this to be included in that series, > TBH, this patch make more sense along with that series than by itself. No it doesn't. This is no different than converting to devm_* variants or other cleanups to match current preferred styles. Treewide cross subsystem clean-ups are a huge pain to merge. Why would you ask for that when it is clearly not necessary? Rob