Received: by 2002:a05:6a10:a841:0:0:0:0 with SMTP id d1csp1310566pxy; Fri, 23 Apr 2021 05:24:28 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzvlbSh4zKBES+nkm3GJC5UKHUW1iOUm4+k9O6esdq9He0S/B4vTdyqVXfTX4yZE3fYTr/T X-Received: by 2002:a05:6402:441:: with SMTP id p1mr4229541edw.298.1619180668118; Fri, 23 Apr 2021 05:24:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1619180668; cv=none; d=google.com; s=arc-20160816; b=W6sMqKUZzBjgE/LS2IMki3EDWWihT4RTCPCmXwZVUtBCjNjEMAIFwGNHSoeKWom42B oYx0FJzWnhuZoCMrHbpjHhfBd6eSwOULXO2p3D/VefjegCWs7pR9ZREFckiiJM5rlJu+ fmafWYz7IFcSor6aN4jXhGDEEcvX7B2TxjCp3MDccjwTYF55VPDiDy7Tdzmfuk61Ff3U OQ1Bbfcj5FSp9LqY4TPHIBxGNLuLGnTpAgZQVcJcxR8K9Cy0hAqwNGWs61drCr6UOm5a aKRwdbAky7vOt1l6zLYNeKNzRE2a8oWfVj0Pw9YvQUPu/i71Hg75TEINIcNTWcow/jvD YCWw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=4LzO873lNsIvzTGUTP/79STOwZaeMBOW4tfU+5JYKeY=; b=EgIw9WzN0P6dpTHS4wYlbNttaG9bE8N5Cots3e1/gXPr6m/pPeJytWNnWFDyGf96Jw qcOtd9z5OisP2awTl81PP2Qe5PKiE7gQhPoi76uJK8rtq6EJT26G7T8wkAzMmnFUmtMW z4vSWvpw2Zapvqm1on2vgIvIM2xsfEBk+kWEu16tZoYoWtDCyBepJU0EX34Lgn9P3dvL WAcFLzuwhl5xggq93s8Lk6LIE1qXiGd4SYiFW3D7SaJw2bnqiBuk2kPqBWM+HRZciZtr LOpHuQFLINF9HTr1QQu7duyexgLOM2ey90XbnMrxI+1L0myRt+FEkDUdqcoP6A2ott+x guGA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id cq27si5131265edb.454.2021.04.23.05.24.04; Fri, 23 Apr 2021 05:24:28 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242497AbhDWMXW (ORCPT + 99 others); Fri, 23 Apr 2021 08:23:22 -0400 Received: from elvis.franken.de ([193.175.24.41]:38492 "EHLO elvis.franken.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231315AbhDWMXK (ORCPT ); Fri, 23 Apr 2021 08:23:10 -0400 Received: from uucp (helo=alpha) by elvis.franken.de with local-bsmtp (Exim 3.36 #1) id 1lZupM-00019R-00; Fri, 23 Apr 2021 14:22:32 +0200 Received: by alpha.franken.de (Postfix, from userid 1000) id 93878C0AC8; Fri, 23 Apr 2021 13:47:28 +0200 (CEST) Date: Fri, 23 Apr 2021 13:47:28 +0200 From: Thomas Bogendoerfer To: xiaochuan mao Cc: Rob Herring , Qing Zhang , Jiaxun Yang , devicetree@vger.kernel.org, linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] MIPS:DTS:Fix label name and interrupt number of ohci for Loongson-2K Message-ID: <20210423114728.GA8582@alpha.franken.de> References: <20210423015234.23870-1-maoxiaochuan@loongson.cn> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210423015234.23870-1-maoxiaochuan@loongson.cn> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Apr 23, 2021 at 09:52:34AM +0800, xiaochuan mao wrote: > from Loongson-2K1000 user manual know that under pci bus > the device num is 4, function number is 2 and register is 0x2200 > is ohci. the ohci interrupt number is 51. because Loongson-2K1000 has > 64 interrupt sources, 0-31 correspond to the device tree liointc0 device > node, and the other correspond to liointc1 node. so it should be > number 19 correspon to liointc1. > > Signed-off-by: xiaochuan mao > --- > arch/mips/boot/dts/loongson/loongson64-2k1000.dtsi | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) applied to mips-next. Thomas. -- Crap can work. Given enough thrust pigs will fly, but it's not necessarily a good idea. [ RFC1925, 2.3 ]