Re: [PATCH V2 0/2] ACPI: Add LoongArch-related definitions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi, Rafael,

On Wed, Mar 9, 2022 at 1:29 PM Huacai Chen <chenhuacai@xxxxxxxxx> wrote:
>
> Hi, Rafael,
>
> On Wed, Mar 9, 2022 at 2:49 AM Rafael J. Wysocki <rafael@xxxxxxxxxx> wrote:
> >
> > On Sun, Mar 6, 2022 at 12:17 PM Huacai Chen <chenhuacai@xxxxxxxxxxx> wrote:
> > >
> > > LoongArch is a new RISC ISA, which is a bit like MIPS or RISC-V.
> > > LoongArch includes a reduced 32-bit version (LA32R), a standard 32-bit
> > > version (LA32S) and a 64-bit version (LA64). LoongArch use ACPI as its
> > > boot protocol LoongArch-specific interrupt controllers (similar to APIC)
> > > are already added in the next revision of ACPI Specification (current
> > > revision is 6.4).
> > >
> > > This patchset are preparing to add LoongArch support in mainline kernel,
> > > we can see a snapshot here:
> > > https://github.com/loongson/linux/tree/loongarch-next
> > >
> > > Cross-compile tool chain to build kernel:
> > > https://github.com/loongson/build-tools/releases
> > >
> > > Loongson and LoongArch documentations:
> > > https://github.com/loongson/LoongArch-Documentation
> > >
> > > ECR for LoongArch-specific interrupt controllers:
> > > https://mantis.uefi.org/mantis/view.php?id=2203
> > > https://mantis.uefi.org/mantis/view.php?id=2313
> > >
> > > ACPI changes of LoongArch have been approved in the last year, but the
> > > new version of ACPI SPEC hasn't been made public yet.
> > >
> > > V2: Remove merged patches and update commit messages.
> > >
> > > Huacai Chen and Jianmin Lv(2):
> > >  ACPICA: MADT: Add LoongArch APICs support.
> > >  ACPICA: Events: Support fixed pcie wake event.
> >
> > Both patches in this series are mostly ACPICA material which needs to
> > be submitted to the upstream ACPICA project via
> > https://github.com/acpica/acpica
> >
> > It will be pulled by the Linux kernel from there.
> I found that you are also a maintainer of the ACPICA project, do you
> mean I should submit by github PR, not by maillist?
I submit ACPICA project, please review:
https://github.com/acpica/acpica/pull/757

Huacai
>
> >
> > >
> > > Signed-off-by: Huacai Chen <chenhuacai@xxxxxxxxxxx>
> > > Signed-off-by: Jianmin Lv <lvjianmin@xxxxxxxxxxx>
> > > ---
> > >  drivers/acpi/acpica/evevent.c  |  17 ++++--
> > >  drivers/acpi/acpica/hwsleep.c  |  12 ++++
> > >  drivers/acpi/acpica/utglobal.c |   4 ++
> > >  drivers/acpi/tables.c          |  10 ++++
> >
> > This tables.c change can be submitted as a separate patch when the
> > ACPICA changes get integrated.
> Do you mean split the first patch into .h parts and .c parts, then
> submit the .h parts and the second patch by github PR, then submit the
> .c parts of the first patch by maillist?
>
> Huacai
> >
> > >  include/acpi/actbl2.h          | 125 ++++++++++++++++++++++++++++++++++++++++-
> > >  include/acpi/actypes.h         |   3 +-
> > >  6 files changed, 163 insertions(+), 8 deletions(-)
> > > --
> > > 2.27.0
> > >



[Index of Archives]     [Linux IBM ACPI]     [Linux Power Management]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux