All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tony Huang 黃懷厚" <tony.huang@sunplus.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "Tony Huang" <tonyhuang.sunplus@gmail.com>,
	"derek.kiernan@xilinx.com" <derek.kiernan@xilinx.com>,
	"dragan.cvetic@xilinx.com" <dragan.cvetic@xilinx.com>,
	"arnd@arndb.de" <arnd@arndb.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"devicetree@vger.kernel.org" <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:22:01 +0000	[thread overview]
Message-ID: <2e7d5df0cbe74f2697709ed3e8c94b0b@sphcmbx02.sunplus.com.tw> (raw)
In-Reply-To: <Ya3EjykU5RMaRbkt@kroah.com>

Dear Greg KH:

> -----Original Message-----
> From: Greg KH <gregkh@linuxfoundation.org>
> Sent: Monday, December 6, 2021 4:07 PM
> To: Tony Huang 黃懷厚 <tony.huang@sunplus.com>
> Cc: Tony Huang <tonyhuang.sunplus@gmail.com>; derek.kiernan@xilinx.com;
> dragan.cvetic@xilinx.com; arnd@arndb.de; linux-kernel@vger.kernel.org;
> robh+dt@kernel.org; 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 06, 2021 at 06:48:46AM +0000, Tony Huang 黃懷厚 wrote:
> > Dear Greg KH, Arnd:
> >
> > > -----Original Message-----
> > > From: Greg KH <gregkh@linuxfoundation.org>
> > > Sent: Friday, December 3, 2021 6:39 PM
> > > To: Tony Huang <tonyhuang.sunplus@gmail.com>
> > > Cc: derek.kiernan@xilinx.com; dragan.cvetic@xilinx.com;
> > > arnd@arndb.de; linux-kernel@vger.kernel.org; robh+dt@kernel.org;
> > > devicetree@vger.kernel.org; Wells Lu 呂芳騰 <wells.lu@sunplus.com>;
> > > Tony Huang 黃懷厚
> > > <tony.huang@sunplus.com>
> > > Subject: Re: [PATCH v2 2/2] misc: Add iop driver for Sunplus SP7021
> > >
> > > On Fri, Dec 03, 2021 at 11:48:45AM +0800, Tony Huang wrote:
> > > > IOP (IO Processor) embedded inside SP7021 which is used as
> > > > Processor for I/O control, RTC wake-up and cooperation with CPU &
> > > > PMC in power management purpose.
> > > > The IOP core is DQ8051, so also named IOP8051, it supports
> > > > dedicated JTAG debug pins which share with SP7021.
> > > > In standby mode operation, the power spec reach 400uA.
> > > >
> > > > Signed-off-by: Tony Huang <tonyhuang.sunplus@gmail.com>
> > > > ---
> > > > Changes in v2:
> > > >  - Addressed comments from Arnd Bergmann.
> > > >  - Addressed comments from Greg KH.
> > > >  - Addressed comments from kernel test robot.
> > > >
> > > >  MAINTAINERS                    |   1 +
> > > >  drivers/misc/Kconfig           |   1 +
> > > >  drivers/misc/Makefile          |   1 +
> > > >  drivers/misc/iop/Kconfig       |  13 ++
> > > >  drivers/misc/iop/Makefile      |   6 +
> > >
> > > Why do you need a subdirectory for a single .c file?
> > >
> >
> > 1. Currently my bin file is placed in the root file system. I need to
> > wait for the kernel booting to succeed before loading the bin code.
> 
> What "bin file"?
> 

IOP MODULE EXECUTES 8051 CODE
Source code should reserve SDRAM memory area for IOP module code. 8051 bin file normal code and standby code can be placed in this area. The location area can be select by user.
Normal code: Monitor CPU commands.
Standby code: For RTC wake up, cooperation with CPU&PMC in power management When the system enters standby mode, 8051 bin file should be moved to I_Cache.
I_Cache has 16K only. Standby code cannot exceed 16K.
When the IOP module is mounted, CPU load 8051 codes (normal.bin) into memory.
Iop_base_addr_l and iop_base_addr_h specify address.
During system boot up, when the IOP is mounted, it will load 8051 normal code and start execute 8051 code.

> > 2. In addition, I need the kernel booting process to be able to mount
> > the iop module and load bin file.I need to put bin file in /iop.
> 
> That is an odd directory location.
> 
> > Do you have a good way to load bin code during kernel booting?
> 
> Is this firmware?  Put it in the normal location for firware that the kernel
> expects to see.
> 
> thanks,
> 
> greg k-h

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

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-03  3:48 [PATCH v2 0/2] Add iop driver for Sunplus SP7021 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  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 黃懷厚 [this message]
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 黃懷厚

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=2e7d5df0cbe74f2697709ed3e8c94b0b@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.