public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: fuyao <fuyao@allwinnertech.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 回复:[PATCH] cpuidle: add riscv cpuidle driver
Date: Mon, 28 Sep 2020 17:26:54 +0800	[thread overview]
Message-ID: <20200928092654.GB4756@g8Exdroid64> (raw)
In-Reply-To: <58abe153-689d-460c-a119-91270cd110cf.liush@allwinnertech.com>

On Mon, Sep 14, 2020 at 08:58:02PM +0800, 刘邵华BTD wrote:
> Hi Daniel,
> > > This patch adds a cpuidle driver for systems based RISCV architecture.
> > > This patch supports state WFI. Other states will be supported in the
> > > future.
> > > 
> > > Signed-off-by: liush <liush@allwinnertech.com>
> > > ---
> > 
> > [ ... ]
> > 
> > >  
> > >  obj-$(CONFIG_RISCV_M_MODE) += traps_misaligned.o
> > > diff --git a/arch/riscv/kernel/cpuidle.c b/arch/riscv/kernel/cpuidle.c
> > > new file mode 100644
> > > index 00000000..a3289e7
> > > --- /dev/null
> > > +++ b/arch/riscv/kernel/cpuidle.c
> > > @@ -0,0 +1,8 @@
> > > +// SPDX-License-Identifier: GPL-2.0
> > > +#include <asm/cpuidle.h>
> > > +
> > > +void cpu_do_idle(void)
> > > +{
> > > + __asm__ __volatile__ ("wfi");
> > > +
> > 
> > extra line
> > 
> > > +}
> 
> > As for the next deeper states should end up with the cpu_do_idle
> > function, isn't there an extra operation with the wfi() like flushing
> > the l1 cache?
> 
> Data cache consistency is mainly ensured by hardware in riscv, and there is no 
> implementation of flushing data cache in kernel. Before wfi(),add an memory 
> barrier operation - mb(). Is this feasible? 
> 
>   //arch/riscv/include/asm/barrier.h
> 
>   17 #define RISCV_FENCE(p, s) \
>   18         __asm__ __volatile__ ("fence " #p "," #s : : : "memory")
>   19 
>   20 /* These barriers need to enforce ordering on both devices or memory. */                                                                                                            
>   21 #define mb()            RISCV_FENCE(iorw,iorw) 
> 
> 
> After modification, the codes is as follows.
> 
> 81 @@ -0,0 +1,8 @@
> 82 +// SPDX-License-Identifier: GPL-2.0
> 83 +#include <asm/cpuidle.h>
> 84 +
> 85 +void cpu_do_idle(void)
> 86 +{
> 87 +       mb();
take a sceptical attibute with it , anyway mb() shout comment it with why
> 88 +       __asm__ __volatile__ ("wfi");
> 89 +
> 90 +}
> 
> > > diff --git a/drivers/cpuidle/Kconfig b/drivers/cpuidle/Kconfig
> > > index c0aeedd..f6be0fd 100644
> > > --- a/drivers/cpuidle/Kconfig
> > > +++ b/drivers/cpuidle/Kconfig
> > > @@ -62,6 +62,11 @@ depends on PPC
> > >  source "drivers/cpuidle/Kconfig.powerpc"
> > >  endmenu
> > >  
> > > +menu "RISCV CPU Idle Drivers"
> > > +depends on RISCV
> > > +source "drivers/cpuidle/Kconfig.riscv"
> > > +endmenu
> > > +
> > >  config HALTPOLL_CPUIDLE
> > >   tristate "Halt poll cpuidle driver"
> > >   depends on X86 && KVM_GUEST
> > > diff --git a/drivers/cpuidle/Kconfig.riscv b/drivers/cpuidle/Kconfig.riscv
> > > new file mode 100644
> > > index 00000000..e86d36b
> > > --- /dev/null
> > > +++ b/drivers/cpuidle/Kconfig.riscv
> > > @@ -0,0 +1,11 @@
> > > +# SPDX-License-Identifier: GPL-2.0-only
> > > +#
> > > +# RISCV CPU Idle drivers
> > > +#
> > > +config RISCV_CPUIDLE
> > > +        bool "Generic RISCV CPU idle Driver"
> > > +        select DT_IDLE_STATES
> > > + select CPU_IDLE_MULTIPLE_DRIVERS
> > > +        help
> > > +          Select this option to enable generic cpuidle driver for RISCV.
> > > +   Now only support C0 State.
> > 
> > Identation
> 
> I'll fix it. Thank you!

-- 
<http://www.allwinnertech.com> Allwinnertech Technology



  reply	other threads:[~2020-09-28  9:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14  1:52 [PATCH] cpuidle: add riscv cpuidle driver liush
2020-09-14  5:46 ` Daniel Lezcano
2020-09-14 12:58   ` 回复:[PATCH] " 刘邵华BTD
2020-09-28  9:26     ` fuyao [this message]
2020-09-14  8:40 ` [PATCH] " Anup Patel
2020-09-14 13:00   ` 回复:[PATCH] " 刘邵华BTD
2020-09-14 22:08 ` [PATCH] " Palmer Dabbelt
2020-09-15 12:59   ` 回复:[PATCH] " 刘邵华BTD
2020-09-16  1:27   ` liush

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=20200928092654.GB4756@g8Exdroid64 \
    --to=fuyao@allwinnertech.com \
    --cc=linux-kernel@vger.kernel.org \
    /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