Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp3687418iob; Mon, 2 May 2022 03:06:41 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyEZH2H4xU2CviU2+IiS1UBurQ9IJOstOiR4gSBEuxmZj1Q0qc6aTr4c7AZUy3QIua4QVWf X-Received: by 2002:ac2:5f84:0:b0:471:fd0f:a6e7 with SMTP id r4-20020ac25f84000000b00471fd0fa6e7mr8426478lfe.41.1651486000695; Mon, 02 May 2022 03:06:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1651486000; cv=none; d=google.com; s=arc-20160816; b=UcjR4hxYCOcxeZ2aQ++faRP8zP1EnhWyoh2aYUTkwyJvHBJIC/TU1H3U1aQiJODjke dpre5oTQBIiRFKaei87pYdR4Xy2E28cqONxQsooj4RXC6f3ANwqFYCL+9BtkWR+akuy5 T1LM5eIkMOsYiVaIo6hymuFyI4C1sN0TIt5zBId7j7nwVzyTLDVMFExHgYJlK8Tz+a3M TO9UR0SDtTmoKgfqkniP+rTrU1b2/ignlPaqk+qpnD+GRhPUhrQYMhCOs08KPAviOs5o mq+yRWJyjBZTwsr7lPofioMhF1RmHRidJu+hPaOuHzIkap/KjdiNqrr4Gp9kyo/pU/K9 h+zQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:organization :references:cc:to:from:subject:dkim-filter; bh=oS9pfnuPEawdPiZNzZFQdIhd3FjzwVB0WFJfw/gu+I0=; b=sWWad0ZFPWuY+yiwqAUaCzpOmF24GUOY98qGSBtiFeAvZPVSRS7jYbqjFF0rG0K5Mf LHRPCaFheTfNfe0qD12SRvpT1wRb1f1RFZzZw/oMeQYIITjUzSf8OuQXGsG43O5Mwvap TqiA1Y6Z6YFo6fnqzH0cple4gB81wqcra5c0iHpuDDHu6CsshkpxXbXjBhMk/BM1Kq+v 1d3XQSIlvlS+935G1kz3yKdQ+ftzIvMoq//vWjHIXIBdPST8hbTeRjAgSbNAlX9ybUHn f37baIRSSA9vEChEnDVva8TuXd3TJNhxOC7Sxdll86/ZUSCaQ1TyZYNX4iNGXRQT4BLI vwpw== 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 h2-20020a0565123c8200b004722dd11721si19754401lfv.30.2022.05.02.03.06.13; Mon, 02 May 2022 03:06:40 -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 S1345775AbiEASM4 (ORCPT + 99 others); Sun, 1 May 2022 14:12:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49220 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230050AbiEASMy (ORCPT ); Sun, 1 May 2022 14:12:54 -0400 Received: from mxout03.lancloud.ru (mxout03.lancloud.ru [45.84.86.113]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 778AE4EA38; Sun, 1 May 2022 11:09:27 -0700 (PDT) Received: from LanCloud DKIM-Filter: OpenDKIM Filter v2.11.0 mxout03.lancloud.ru 7302120EA55E Received: from LanCloud Received: from LanCloud Received: from LanCloud Subject: Re: [PATCH v3] sh: avoid using IRQ0 on SH3/4 From: Sergey Shtylyov To: Rich Felker , John Paul Adrian Glaubitz CC: , , Yoshinori Sato , Greg Kroah-Hartman References: <2584ba18-9653-9310-efc1-8b3b3e221eea@omp.ru> <11021433-66c0-3c56-42bd-207a5ae8d267@physik.fu-berlin.de> <20220429171623.GQ7074@brightrain.aerifal.cx> <525e7383-d26a-fe35-7005-e1dd9b57f76f@omp.ru> Organization: Open Mobile Platform Message-ID: <86b6c752-0599-d878-bff4-7d3d7b84176a@omp.ru> Date: Sun, 1 May 2022 21:09:24 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 MIME-Version: 1.0 In-Reply-To: <525e7383-d26a-fe35-7005-e1dd9b57f76f@omp.ru> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [192.168.11.198] X-ClientProxiedBy: LFEXT02.lancloud.ru (fd00:f066::142) To LFEX1907.lancloud.ru (fd00:f066::207) X-Spam-Status: No, score=-3.9 required=5.0 tests=BAYES_00,NICE_REPLY_A, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE,UNPARSEABLE_RELAY 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 5/1/22 8:58 PM, Sergey Shtylyov wrote: [...] >>>> Using IRQ0 by the platform devices is going to be disallowed soon (see [1]) >>>> and even now, when IRQ0 is about to be returned by platfrom_get_irq(), you >>>> see a big warning. The code supporting SH3/4 SoCs maps the IRQ #s starting >>>> at 0 -- modify that code to start the IRQ #s from 16 instead. >>>> >>>> The patch should mostly affect the AP-SH4A-3A/AP-SH4AD-0A boards as they >>>> indeed use IRQ0 for the SMSC911x compatible Ethernet chip... >>> >>> Maybe try getting it landed through Andrew Morton's tree? >> >> Hi. I'm alive and looking at it. If it needs to go in for this cycle I >> will send a pull request for just this and anything else critical. Was > > Well, now using IRQ0 just causes a WARNing in platform_get_irq() -- I don't > think fixing it is critical enough. Starting from 5.19-rc1 the SMSC91xx driver > should stop working on the mentioned boards. > But let me look at the SMSC driver itself, I haven't done this yet... Looks like these boards were borked back in 2015 by this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=965b2aa78fbcb831acf4f669f494da201f4bcace It stopped accepting IRQ0 for no apparent reason. :-/ [...] >> Rich MBR, Sergey