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 92958C001DB for ; Mon, 7 Aug 2023 13:38:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232406AbjHGNiX (ORCPT ); Mon, 7 Aug 2023 09:38:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53308 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233749AbjHGNh4 (ORCPT ); Mon, 7 Aug 2023 09:37:56 -0400 Received: from mail-yb1-xb35.google.com (mail-yb1-xb35.google.com [IPv6:2607:f8b0:4864:20::b35]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 21C781AD for ; Mon, 7 Aug 2023 06:37:55 -0700 (PDT) Received: by mail-yb1-xb35.google.com with SMTP id 3f1490d57ef6-d465b3d50efso1648116276.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=IRzD6xmbXe4itkjQq5F6vS0ULBCHefrE1Z4htUGucrbhDaBRuCr5WAt0PIWO9dkzPj gvIs53DDQRdJH9O6nq9ZSq0x6aKTu00IhI0KWT6iMOyITtWw+xX1H4uBXSU5Iu6C0n6X 5+FP8qO92WBJWAUPKLdapFV3WXhYxQB2wpGSm6IryZGJegjhnB9hpuNBESKz+Nw5+tnR TIytvFiOqSHzhXk/oV9UdmPKCzBJ7qzDd3vlDc0rGyznlipyP/y/Sg8/W+4XGfqiGbwh Y9Q0ZJf+EcJEpgqMsrqzQ0ANg7UparUJHCmtnIA7S3Kl5bEoBzI+cTbY2v0VYfAKx3qn 20hA== X-Gm-Message-State: AOJu0Yzp+66n9rO5dz9zBU4lyzHubvBobq5zC/k357KGOeLP1whzAYzq bHWhXOB5NeA5R8gQD3m0M5rf4hOpSkOh5qZwloD3Qg== 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: linux-gpio@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