Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp367359iob; Tue, 3 May 2022 20:26:36 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyc0OFlrgB/4vh2QxuvWbLmo7ZAQcpx/ghlq2nsUyl/QX3qIk4hNXNE6dxvJo9E+rYvajef X-Received: by 2002:a05:6402:3d3:b0:426:12cd:ba78 with SMTP id t19-20020a05640203d300b0042612cdba78mr21473503edw.161.1651634796403; Tue, 03 May 2022 20:26:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1651634796; cv=none; d=google.com; s=arc-20160816; b=JggyaXDFAQfMbTzRN3b9LfdjpPSpfDhh1Y5n7FoOt7X0PuUx2K2/FiBccjDO/zVDua 6EHZe73TeIuixr92wSUKljsoWYVlIOYa92T3iaY0JgZwJDsJMf5XfhoO4ra1PfGN9shG CQ8Qu1bZZBC/6jCYEleoMrrO32V/iPHgm8aWuXl5te9kBKG2/XL0eSxh7uqNVI3GmX41 IoII/1kOsmrNoLkxXwzlIQ/Xf+CQDopEiEzq/F4KLPer75SHpAnGuVbI38QtgchNzWoW ER1MRDVn/GfHL3g4mf9naUlzzJZxDK03EEFYk6RXP8X3vVwGUoKJD40zTj5zcPLFkblS qxYQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:references:message-id :in-reply-to:subject:cc:to:from:date; bh=CB1qlvrbqUhewXv4XmftfRm9T/DioKwH4riEXNzDERU=; b=CnT+K5Vabw1pYkswddhGqPlHJmLrVMadBZSFb1TbYGB1AsqlLRgBJcbrOmdfceQQ9A suOgLKGy3Z//o/z2559OFu/+UPS1mgsuOGQLQHErr0uIkWiUDDIJ3nvlalcbj9+0Fpvu NJ1+52rlC7qLKsAqoKNH6m2K2AYN8CwbV/+5dWZU7yLtLc6eV959DhUhlyhWa++wrRmI zKEh7gnBe7AXIVK1JU/66iqk6/GmR4I9VflFIpCjwceoOE8yfGFklnfE6ICuAOFzbAk5 8xhRaXGjqgVYv29AE6TzdECvJWmukXk890ZJOhn7fK+zC4MiN21ypol+aX22whFBancl 3AkQ== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id bf3-20020a0564021a4300b0041d664093e1si14435863edb.482.2022.05.03.20.26.13; Tue, 03 May 2022 20:26:36 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239568AbiECTuW (ORCPT + 99 others); Tue, 3 May 2022 15:50:22 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45604 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233678AbiECTuU (ORCPT ); Tue, 3 May 2022 15:50:20 -0400 Received: from angie.orcam.me.uk (angie.orcam.me.uk [IPv6:2001:4190:8020::34]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id E35AC37A19; Tue, 3 May 2022 12:46:46 -0700 (PDT) Received: by angie.orcam.me.uk (Postfix, from userid 500) id E422292009C; Tue, 3 May 2022 21:46:45 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by angie.orcam.me.uk (Postfix) with ESMTP id E0FA592009B; Tue, 3 May 2022 20:46:45 +0100 (BST) Date: Tue, 3 May 2022 20:46:45 +0100 (BST) From: "Maciej W. Rozycki" To: Geert Uytterhoeven cc: Rob Landley , John Paul Adrian Glaubitz , Sergey Shtylyov , Rich Felker , Linux-sh list , Linux Kernel Mailing List , Yoshinori Sato , Greg Kroah-Hartman Subject: Re: [PATCH v3] sh: avoid using IRQ0 on SH3/4 In-Reply-To: Message-ID: References: <2584ba18-9653-9310-efc1-8b3b3e221eea@omp.ru> <11021433-66c0-3c56-42bd-207a5ae8d267@physik.fu-berlin.de> <2ebef1ac-e5c5-980c-9413-22a6cccdfa1d@landley.net> <2a3f8b4c-2c0d-28bc-8dcd-c56c7b8a2bb4@landley.net> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,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 On Tue, 3 May 2022, Geert Uytterhoeven wrote: > > Sounds like it's now outside of the IRQ range allocation, but I can't find where > > that's requested when registering the controller? (What is a "swizzle" anyway?) > > PCI slots have 4 interrupts (#A, #B, #C, #D). In machines with > multiple slots, the interrupts lines are "swizzled", to avoid that all cards > using a single interrupt are mapped to the same host interrupt. Especially as single-function devices are required to use INTA. Maciej