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 D1214C433EF for ; Tue, 3 May 2022 19:46:49 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229628AbiECTuV (ORCPT ); Tue, 3 May 2022 15:50:21 -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 Precedence: bulk List-ID: X-Mailing-List: linux-sh@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