mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: rui_feng@realsil.com.cn, linux-kernel@vger.kernel.org,
	devel@driverdev.osuosl.org, ricky_wu@realtek.com
Subject: Re: [PATCH] staging: rtsx: Add support for RTS5260
Date: Fri, 13 Oct 2017 10:54:22 +0100	[thread overview]
Message-ID: <20171013095422.6mql3mso77duoiko@dell> (raw)
In-Reply-To: <20171013092659.GA28241@kroah.com>

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!

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.

In the absence of a subsystem which covers this type of device, I
suggested Misk as a good location to place these drivers.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2017-10-13  9:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-13  8:50 rui_feng
2017-10-13  9:26 ` Greg KH
2017-10-13  9:54   ` Lee Jones [this message]
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
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=20171013095422.6mql3mso77duoiko@dell \
    --to=lee.jones@linaro.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.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

all inboxes | Powered by JetHome®