From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E22D8C00528 for ; Mon, 7 Aug 2023 13:38:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231847AbjHGNiX (ORCPT ); Mon, 7 Aug 2023 09:38:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53312 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233831AbjHGNh4 (ORCPT ); Mon, 7 Aug 2023 09:37:56 -0400 Received: from mail-yb1-xb36.google.com (mail-yb1-xb36.google.com [IPv6:2607:f8b0:4864:20::b36]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 24A2F10D5 for ; Mon, 7 Aug 2023 06:37:55 -0700 (PDT) Received: by mail-yb1-xb36.google.com with SMTP id 3f1490d57ef6-d465b3d50efso1648117276.1 for ; Mon, 07 Aug 2023 06:37:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1691415474; x=1692020274; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=whejdASkJGYmLZxS+FlOqF2f/J1Rdm5EDe6V5ST3LuQ=; b=gZ+36WDDT3vFYnLcSlRKa/NuShCqLSSyXuRIKuBCcK2PB75SwhpLFE5DGSxZtR3+GQ MWZ9PJtesN4mNZjrT3daZc6cH+e6gL+BYTJKIjTCg4n1uJf1Qe/y/4FDjHr19M2fiDXw btkW4xbEeiAXJuuLmeNCwl4FV89XQRUsnGARA2nH2TkNpUwOFAWQXPzuZIM7YNjPS0Sp 9+apZXATVERqCRT4T+sJcS7UArh2Kzsq8gcplqQxBivztk9N5AvMLC5hFea2wA6Q4vXO dHK5qEpjuCPIjMHzBqgUoiYsPkyBk2sf5uPz6/tSmJkg8yqAK7fkhNXcjLPZhlVx/lFh UUXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691415474; x=1692020274; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=whejdASkJGYmLZxS+FlOqF2f/J1Rdm5EDe6V5ST3LuQ=; b=SmHQDVfVjNXCXjTnjSXp/r/Y1UTJsXonDPFVMB4nD7kEx9O1pGPEkxeXXqSmkPc0nH EQY0mblyoCeEnujjBkQDWcYC7BaslJUETuo7q1fMIjGiXRWOBmJk6166d9OsWskklW5+ PXKZjCTqXHXYkuIZCb9gi6gsRP3cpbMKQKVaMHanRJp7EsP+ImzV9gQbmx1DwBiuLoEX WBjtBHkDgJZpFVahPcXYfebN4B3m3gD5zXcBM+LmIpcuUu9ci+kyO0KmGih8WP06A+E5 GYgiHIaEHsNGw2Ye2yB8DQYGEdIyTNS0x04IHuECyYR858AhT0X65tFRw7u3SkvAMlkj EiBA== X-Gm-Message-State: AOJu0YwvECTUMd5tYvFzFlQWvdKSj5OD+s41YYD3Z8vqvVLOm4pIkfdC O41s7rC5LoaODdavCq5yoNOggfBADxllGD5DO78mBQ== X-Google-Smtp-Source: AGHT+IF8qFOkXRjcLVqPSJs0Dcjy+XexfZt9JpoPqlbfN68UupareNNAKBdj08K5cz1GN8sYL8dyB/+6maviIRw0lVg= X-Received: by 2002:a25:4256:0:b0:d0a:fa7f:2fbf with SMTP id p83-20020a254256000000b00d0afa7f2fbfmr7826923yba.48.1691415474298; Mon, 07 Aug 2023 06:37:54 -0700 (PDT) MIME-Version: 1.0 References: <20230724060108.1403662-1-huqiang.qin@amlogic.com> In-Reply-To: <20230724060108.1403662-1-huqiang.qin@amlogic.com> From: Linus Walleij Date: Mon, 7 Aug 2023 15:37:43 +0200 Message-ID: Subject: Re: [PATCH V2 0/3] Add binding header file for GPIO interrupt of Amlogic Meson-G12A To: Huqiang Qin Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org, neil.armstrong@linaro.org, khilman@baylibre.com, jbrunet@baylibre.com, martin.blumenstingl@googlemail.com, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On Mon, Jul 24, 2023 at 8:02=E2=80=AFAM Huqiang Qin wrote: > After adding this binding header file, you can intuitively find > the interrupt number corresponding to each GPIO, and apply it > in the format of IRQID_XXX where it needs to be used. (...) > Huqiang Qin (3): > dt-bindings: interrupt-controller: Add header file for Amlogic > Meson-G12A SoCs > pinctrl: Replace the IRQ number in the driver with the IRQID macro > definition > arm64: dts: Replace the IRQ number with the IRQID macro definition Neil wrote: > What's the best way to apply this patchset ? I just applied all three to the pin control tree. I could have applied just the two first and then offered an immutable branch. But eh... too much work for too low risk. Better to just apply it and hope all works out. If it explodes I just back out and figure something like the above. Yours, Linus Walleij