From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Bjorn Helgaas" <helgaas@kernel.org>,
"Huacai Chen" <chenhuacai@loongson.cn>,
arnd@kernel.org
Cc: "Bjorn Helgaas" <bhelgaas@google.com>,
linux-pci <linux-pci@vger.kernel.org>,
"Xuefeng Li" <lixuefeng@loongson.cn>,
"Huacai Chen" <chenhuacai@gmail.com>,
linux-arch@vger.kernel.org
Subject: LoongArch (was: Re: [PATCH V2 2/4] PCI: Move loongson pci quirks to quirks.c)
Date: Sun, 06 Jun 2021 16:14:24 +0800 [thread overview]
Message-ID: <2a51e6b8-37e5-43cb-b0b4-d6fdd1848fe3@www.fastmail.com> (raw)
In-Reply-To: <20210605211529.GA2326325@bjorn-Precision-5520>
在2021年6月6日六月 上午5:15，Bjorn Helgaas写道：
+linux-arch and Arnd for arch related discussions
>
> If you're moving these from device-specific file to a generic file,
> these #defines now need to have device-specific names.
>
> But these appear to be for built-in hardware that can only be present
> in Loongson (I assume mips?) systems. If that's the case, maybe they
> should go to a mips-specific file like arch/mips/pci/quirks.c?
>
> But I see you see you mention LoongArch above, so I don't know if
> that's part of arch/mips, or if there's an arch/loongson coming, or
> what.
As far as I read LoongArch should be a brand new RISC architecture.
I saw Loongson release some documents[1] and code[2] regarding this
new architecture.
Huacai, as you are submitting these code, does it mean Loongson intends
to mainline LoongArch kernel?
If so, I'm certain that there is a lot of drivers and other code can be
reused between MIPS part and LoongArch part for Loongson chips.
Could you please make an announcement about your plans?
Thanks.
[1]: https://github.com/loongson/LoongArch-Documentation
[2]: https://github.com/loongarch64
--
- Jiaxun
next parent reply other threads:[~2021-06-06 8:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210605211529.GA2326325@bjorn-Precision-5520>
2021-06-06 8:14 ` Jiaxun Yang [this message]
2021-06-07 0:51 ` LoongArch (was: Re: [PATCH V2 2/4] PCI: Move loongson pci quirks to quirks.c) Huacai Chen
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=2a51e6b8-37e5-43cb-b0b4-d6fdd1848fe3@www.fastmail.com \
--to=jiaxun.yang@flygoat.com \
--cc=arnd@kernel.org \
--cc=bhelgaas@google.com \
--cc=chenhuacai@gmail.com \
--cc=chenhuacai@loongson.cn \
--cc=helgaas@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lixuefeng@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).