From: "Tony Huang 黃懷厚" <tony.huang@sunplus.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: DTML <devicetree@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Derek Kiernan" <derek.kiernan@xilinx.com>,
"Dragan Cvetic" <dragan.cvetic@xilinx.com>,
"Rob Herring" <robh+dt@kernel.org>,
gregkh <gregkh@linuxfoundation.org>,
"Wells Lu 呂芳騰" <wells.lu@sunplus.com>,
黃懷厚 <tonyhuang.sunplus@gmail.com>
Subject: RE: [PATCH v4 2/2] misc: Add iop driver for Sunplus SP7021
Date: Fri, 17 Dec 2021 11:03:36 +0000 [thread overview]
Message-ID: <d7db8a508e9b4eb8933f4862087919b2@sphcmbx02.sunplus.com.tw> (raw)
In-Reply-To: <CAK8P3a0cA7iL=ug6hiqWAV1-qFSoCN-R7jrXv0cqByUDJV4x0Q@mail.gmail.com>
Dear Arnd:
>
> > 3.So you ask me to control IOP(8051) through file_operations, not
> > through DEVICE_ATTR
>
> No, neither of them. Use the appropriate drivers/*/ subsystems for any
> functionality that has an existing subsystem. If there is something that the iop
> does that does not yet have a subsystem, that requires a more thorough design
> discussion for creating a new user interface, ideally in a hardware-independent
> way. You should not start with that until all the normal features (rtc, wakeup,
> suspend, gpio, ...) are supported.
>
IOP(8051) has 12 bytes Mailbox registers, which can be read and written by IOP(8051) and System, used to exchange information with the system, faster than shared memory.
Thanks
next prev parent reply other threads:[~2021-12-17 11:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 2:34 [PATCH v4 0/2] " Tony Huang
2021-12-16 2:34 ` [PATCH v4 1/2] dt-binding: misc: Add iop yaml file " Tony Huang
2021-12-16 2:35 ` [PATCH v4 2/2] misc: Add iop driver " Tony Huang
[not found] ` <YbrsbtBgUDnjZJ/o@kroah.com>
[not found] ` <CAHpW4oRTcXq6k2o4cjFeHznZrR737947UPE60nWyPTRLPTR0Gw@mail.gmail.com>
2021-12-17 8:10 ` Tony Huang 黃懷厚
2021-12-17 8:24 ` gregkh
2021-12-20 8:35 ` Tony Huang 黃懷厚
[not found] ` <CAK8P3a0CnCK-Dfodp-jTzZApM_1NpdY7DV2fRqnO=gaju5xGwg@mail.gmail.com>
[not found] ` <CAHpW4oQmtd-gG1HYZT-Dk=QAvXKsKebzcOaVtrEeoujwoL9zSg@mail.gmail.com>
[not found] ` <316c16afbff74160b07bd74444f3b8e1@sphcmbx02.sunplus.com.tw>
2021-12-17 6:54 ` gregkh
2021-12-17 8:12 ` Arnd Bergmann
2021-12-17 10:24 ` Tony Huang 黃懷厚
2021-12-17 11:03 ` Tony Huang 黃懷厚 [this message]
2021-12-22 7:20 ` 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=d7db8a508e9b4eb8933f4862087919b2@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®