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 X-Spam-Level: X-Spam-Status: No, score=-3.9 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id DF0DAC388F9 for ; Wed, 11 Nov 2020 14:10:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 853052074B for ; Wed, 11 Nov 2020 14:10:47 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="THd6YZbK" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726902AbgKKOJ6 (ORCPT ); Wed, 11 Nov 2020 09:09:58 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59550 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726412AbgKKOJc (ORCPT ); Wed, 11 Nov 2020 09:09:32 -0500 Received: from mail-lj1-x242.google.com (mail-lj1-x242.google.com [IPv6:2a00:1450:4864:20::242]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7EA18C0613D1 for ; Wed, 11 Nov 2020 06:09:32 -0800 (PST) Received: by mail-lj1-x242.google.com with SMTP id p12so2209260ljc.9 for ; Wed, 11 Nov 2020 06:09:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=4F6RReVm27W/nhwX00zKDRay2swOnSHsIeTk0Gn+ySk=; b=THd6YZbKXouhcPK7EKGkOIz/sPDjdTWa6OIUxDfH0TaVX5NwEoyp8i74NqBppgZRFY OKy9PBmigzR296Nl3mP7zfsbFF1xxlqHHcw6uatuyCtvcMs3Xqx/kdOhbzZZfEPBDRxu Thndl+h/RBqE2jSttLaubWJkwcl4yIHRA4CMtQ2rjCCe1y+4xUWi1A4ZJfpEnNbO+QM3 I6bmuoHikOnN8ZSoxTf9TSr9le540XckkeZPfmnxfSJuljSLhoQOd5Cl6efDQBrARvlo 1wfr4Xp3wGwZyffltHH9uMOdrXWHWds+e1Tfh+p/eyo5ISA43ZdK3EPp9hXYBX/idEDU Po+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4F6RReVm27W/nhwX00zKDRay2swOnSHsIeTk0Gn+ySk=; b=rr7w7tX6+xqsSah53Lj8/qlDe8uabV85yZ/yJgRAjMvqN2vzBoxutfsdLts5TmHMMz R/6Izd86rHmytOX1+YvAjGx3ri9h5kt8OToMeILCwAWdYb9QTYzAfdKfpy19+Jo/p5yy dY3rokWBvFVJGNHJzOUXhLhPB08NCD0rWxWmexYBHWqgVp/+hwTIMfxikgosHv9LsJBN VvZFUQ7/LXs8kS1it7jFuk7M5kMPKjuHVx4JfCpWjKQMKyywlcqUqQSxQC5zTTSOU+60 trvDbWaEAufxaDrakGqoOvYexUnH0HCqsK2Z16TCbU6xU4rkZZiAjQCRGUehkBVGZNx2 Imww== X-Gm-Message-State: AOAM532AQrYP+0x0zcy9Ph3ZFNKAm6fDco0OPLc6hsx5oBsGc0pdPCex +zi7ypsE1g8lOSmmT/m5OCKjD/R4JXi+305o+W/4hQ== X-Google-Smtp-Source: ABdhPJwAg11sK3F0ifRwK3lK8O7cB89hYdWEnxHVyWaVKYaofoDtDv+qsUOkDjyCjd0eZ3pniwiZNWVZVf5qJJP62Uo= X-Received: by 2002:a2e:8604:: with SMTP id a4mr10729544lji.100.1605103770994; Wed, 11 Nov 2020 06:09:30 -0800 (PST) MIME-Version: 1.0 References: <20201019141008.871177-1-daniel@0x0f.com> <20201019141008.871177-4-daniel@0x0f.com> <3fd04aeb5047d8059ddecc1eda19c2e4@kernel.org> <71f3632bee262a18e1b7edb74980ae9a@kernel.org> In-Reply-To: From: Linus Walleij Date: Wed, 11 Nov 2020 15:09:19 +0100 Message-ID: Subject: Re: [PATCH v2 3/5] gpio: msc313: MStar MSC313 GPIO driver To: Marc Zyngier Cc: Daniel Palmer , "open list:GPIO SUBSYSTEM" , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Linux ARM , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org On Tue, Nov 10, 2020 at 3:19 PM Marc Zyngier wrote: > On 2020-11-10 14:02, Linus Walleij wrote: > >> Probably nothing more than setting the callback to > >> irq_chip_set_affinity_parent, > > > > Hm, is this something all GPIO irqchips used on SMP systems > > should be doing? Or just hierarchical ones? > > Probably only the hierarchical ones. I'd expect the non-hierarchical > GPIOs to be muxed behind a single interrupt, which makes it impossible > to move a single GPIO around, and moving the mux interrupt would break > userspace's expectations that interrupts move independently of each > others. I found two suspects and sent patches. I think I might have some more candidates down in pinctrl. I do have some hierarchical IRQ that is on UP systems, I suppose these are not affected. Yours, Linus Walleij