From: Greg KH <gregkh@linuxfoundation.org>
To: 冯锐 <rui_feng@realsil.com.cn>
Cc: Lee Jones <lee.jones@linaro.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"ricky_wu@realtek.com" <ricky_wu@realtek.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 答复: [PATCH] staging: rtsx: Add support for RTS5260
Date: Mon, 16 Oct 2017 09:45:25 +0200 [thread overview]
Message-ID: <20171016074525.GA3044@kroah.com> (raw)
In-Reply-To: <2A308283684ECD4B896628E09AF5361E01A739CE@RS-MBS01.realsil.com.cn>
On Mon, Oct 16, 2017 at 05:58:12AM +0000, 冯锐 wrote:
> > On Fri, Oct 13, 2017 at 10:54:22AM +0100, Lee Jones wrote:
> > > On Fri, 13 Oct 2017, Greg KH wrote:
> > >
> > > > On Fri, Oct 13, 2017 at 04:50:35PM +0800, rui_feng@realsil.com.cn wrote:
> > > > > From: rui_feng <rui_feng@realsil.com.cn>
> > > > >
> > > > > Add support for new chip rts5260.
> > > > > In order to support rts5260,the definitions of some internal
> > > > > registers and workflow have to be modified and are different from
> > > > > its predecessors and OCP function is added for RTS5260.
> > > > > So we need this patch to ensure RTS5260 can work.
> > > > >
> > > > > Signed-off-by: Rui Feng <rui_feng@realsil.com.cn>
> > > >
> > > > Your from and signed-off-by name does not match :(
> > > >
> > > > > ---
> > > > > drivers/mfd/Makefile | 4 +
> > > > > drivers/mfd/rtsx_pcr.c | 127 ++++++-
> > > > > drivers/mfd/rtsx_pcr.h | 12 +
> > > > > drivers/staging/Kconfig | 2 +
> > > > > drivers/staging/rts5260/Kconfig | 6 +
> > > > > drivers/staging/rts5260/rts5260.c | 748
> > > > > ++++++++++++++++++++++++++++++++++++++
> > > > > drivers/staging/rts5260/rts5260.h | 45 +++
> > > > > include/linux/mfd/rtsx_pci.h | 234 +++++++++++-
> > > >
> > > > I do not see a reason why this is a staging driver. Where is the
> > > > TODO file listing what needs to be done to get it out of staging?
> > > > Why can it not just go into the "real" part of the kernel?
> > >
> > > It's not a staging driver. Rui's focus appears to be to have this
> > > driver accepted into Mainline by hook or by crock. He's tried MFD,
> > > Misc and now Staging!
> >
> > Yeah, I've watched it too :)
> >
> > > Background:
> > >
> > > There are a number of drivers in this family which currently reside in
> > > MFD. These were accepted before my time. After a recent review I've
> > > made the decision that these aren't MFD drivers at all.
> > >
> > > MFD drivers are ones which aid in registering and setting up shared
> > > resources for sub-devices which reside on the same piece of silicon.
> > > This driver does basically none of that. Instead it *is* the (what we
> > > describe above as) sub-device. It does everything.
> >
> > I agree with your assessment.
> >
> > > In the absence of a subsystem which covers this type of device, I
> > > suggested Misk as a good location to place these drivers.
> >
> > What type of device is this thing? I can't seem to figure that out. If we can
> > determine that, then we can find the proper place for it in the kernel.
> >
> > Rui, what does this hardware do? What is the interface between the
> > hardware and userspace that this driver is creating?
> >
> This driver is a pcie driver, it bridge mmc subsystem and memstick
> subsystem, and it does not deal with userspace.
Ok, sounds like drivers/misc/ is a good place for it.
thanks,
greg k-h
next prev parent reply other threads:[~2017-10-16 7:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 8:50 [PATCH] staging: rtsx: Add support for RTS5260 rui_feng
2017-10-13 9:26 ` Greg KH
2017-10-13 9:54 ` Lee Jones
2017-10-13 9:59 ` Greg KH
2017-10-13 10:11 ` Lee Jones
2017-10-13 10:21 ` Greg KH
2017-10-13 10:30 ` 答复: " 冯锐
2017-10-16 5:58 ` 冯锐
2017-10-16 7:45 ` Greg KH [this message]
2017-10-13 18:28 ` Mario Limonciello
2017-10-13 21:15 ` Lee Jones
2017-10-16 20:38 ` Mario.Limonciello
2017-10-23 9:18 ` Lee Jones
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=20171016074525.GA3044@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ricky_wu@realtek.com \
--cc=rui_feng@realsil.com.cn \
/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