devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: xiaochuan mao <maoxiaochuan@loongson.cn>
Cc: Rob Herring <robh+dt@kernel.org>,
	Qing Zhang <zhangqing@loongson.cn>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>,
	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
Date: Fri, 23 Apr 2021 13:47:28 +0200	[thread overview]
Message-ID: <20210423114728.GA8582@alpha.franken.de> (raw)
In-Reply-To: <20210423015234.23870-1-maoxiaochuan@loongson.cn>

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 <maoxiaochuan@loongson.cn>
> ---
>  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 ]

      parent reply	other threads:[~2021-04-23 12:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-23  1:52 [PATCH] MIPS:DTS:Fix label name and interrupt number of ohci for Loongson-2K xiaochuan mao
2021-04-23  2:37 ` zhangqing
     [not found]   ` <tencent_A816CB57EADAD19FD3FFC04C3598E81B5608@qq.com>
2021-04-23  4:02     ` 回复: " Jiaxun Yang
2021-04-23  8:19       ` Xiaochuan Mao
2021-04-23 11:47 ` Thomas Bogendoerfer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210423114728.GA8582@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=devicetree@vger.kernel.org \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=maoxiaochuan@loongson.cn \
    --cc=robh+dt@kernel.org \
    --cc=zhangqing@loongson.cn \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).