mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Tony Huang 黃懷厚" <tony.huang@sunplus.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Tony Huang" <tonyhuang.sunplus@gmail.com>,
	"Derek Kiernan" <derek.kiernan@xilinx.com>,
	"Dragan Cvetic" <dragan.cvetic@xilinx.com>,
	gregkh <gregkh@linuxfoundation.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Rob Herring" <robh+dt@kernel.org>,
	DTML <devicetree@vger.kernel.org>,
	"Wells Lu 呂芳騰" <wells.lu@sunplus.com>
Subject: RE: [PATCH v2 2/2] misc: Add iop driver for Sunplus SP7021
Date: Mon, 6 Dec 2021 08:23:41 +0000	[thread overview]
Message-ID: <7e53f347462143669242f9937330fbde@sphcmbx02.sunplus.com.tw> (raw)
In-Reply-To: <CAK8P3a2AgO2R-yQsT6nkiVU0J6pXa-bMnckrShey2EUZjAq3Uw@mail.gmail.com>

Dear Arnd:

> -----Original Message-----
> From: Arnd Bergmann <arnd@arndb.de>
> Sent: Monday, December 6, 2021 4:04 PM
> To: Tony Huang 黃懷厚 <tony.huang@sunplus.com>
> Cc: Arnd Bergmann <arnd@arndb.de>; Tony Huang
> <tonyhuang.sunplus@gmail.com>; Derek Kiernan <derek.kiernan@xilinx.com>;
> Dragan Cvetic <dragan.cvetic@xilinx.com>; gregkh
> <gregkh@linuxfoundation.org>; Linux Kernel Mailing List
> <linux-kernel@vger.kernel.org>; Rob Herring <robh+dt@kernel.org>; DTML
> <devicetree@vger.kernel.org>; Wells Lu 呂芳騰 <wells.lu@sunplus.com>
> Subject: Re: [PATCH v2 2/2] misc: Add iop driver for Sunplus SP7021
> 
> On Mon, Dec 6, 2021 at 4:42 AM Tony Huang 黃懷厚
> <tony.huang@sunplus.com> wrote:
> > > Subject: Re: [PATCH v2 2/2] misc: Add iop driver for Sunplus SP7021
> > > On Fri, Dec 3, 2021 at 4:48 AM Tony Huang
> <tonyhuang.sunplus@gmail.com> wrote:
> > > > +
> > > > +static const struct file_operations sp_iop_fops = {
> > > > +       .owner                  = THIS_MODULE,
> > > > +       .open                   = sp_iop_open,
> > > > +       .read                   = sp_iop_read,
> > > > +       .write                  = sp_iop_write,
> > > > +       .release                = sp_iop_release,
> > > > +};
> > >
> > > This does nothing because all the callbacks are empty. You removed
> > > the inappropriate user space interfaces as I asked you to, but if
> > > there is no way for either kernel or user space to interact with the
> > > hardware, I don't see a point in merging the driver until you add a new
> interface that is usable.
> > >
> >
> > I will modify sp_iop_read() to monitor IOP mailbox data.
> 
> Why is this a useful interface to have? If this is only for debugging, a tracepoint
> may be more useful than a full character device.
> 

Yes, it is for debugging.

> > > Something looks wrong here, maybe reread the documentation for
> > > runtime power management to find a way of putting the device into
> > > low-power mode when it is unused.
> > >
> >
> > When the poweroff command is executed, the run
> > sp_iop_platform_driver_poweroff(void)
> > function will enter the standby mode. The power off will be executed.
> > In the system, IOP can continue to work when other modules in the
> > system enter standby / power down modes to monitor whether the system
> wakes up through RTC.
> 
> Ok, in that case you can probably just remove the empty callback functions.
> 
>          Arnd

      reply	other threads:[~2021-12-06  8:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-03  3:48 [PATCH v2 0/2] " Tony Huang
2021-12-03  3:48 ` [PATCH v2 1/2] dt-binding: misc: Add iop yaml file " Tony Huang
2021-12-03  3:48 ` [PATCH v2 2/2] misc: Add iop driver " Tony Huang
2021-12-03  9:12   ` kernel test robot
2021-12-03 10:38   ` Greg KH
2021-12-06  3:50     ` Tony Huang 黃懷厚
2021-12-06  7:04       ` Greg KH
2021-12-06 15:02         ` Tony Huang 黃懷厚
2021-12-03 10:39   ` Greg KH
2021-12-06  6:48     ` Tony Huang 黃懷厚
2021-12-06  8:06       ` Greg KH
2021-12-06  8:22         ` Tony Huang 黃懷厚
2021-12-06  8:29           ` Greg KH
2021-12-03 10:39   ` Greg KH
2021-12-03 12:17   ` Arnd Bergmann
2021-12-06  3:42     ` Tony Huang 黃懷厚
2021-12-06  8:04       ` Arnd Bergmann
2021-12-06  8:23         ` Tony Huang 黃懷厚 [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=7e53f347462143669242f9937330fbde@sphcmbx02.sunplus.com.tw \
    --to=tony.huang@sunplus.com \
    --cc=arnd@arndb.de \
    --cc=derek.kiernan@xilinx.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dragan.cvetic@xilinx.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=tonyhuang.sunplus@gmail.com \
    --cc=wells.lu@sunplus.com \
    /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

all inboxes | Powered by JetHome®