On Wed, May 24, 2017 at 05:08:10PM +0200, Greg Kroah-Hartman wrote:
> On Wed, May 24, 2017 at 03:54:23PM +0300, Heikki Krogerus wrote:
> > Driver for USB Type-C PHY on Intel WhiskeyCove PMIC that
> > works with Type-C Port Controller Manager to provide USB
> > Power Delivery and USB Type-C functionalities
> > 
> > Signed-off-by: Heikki Krogerus <heikki.kroge...@linux.intel.com>
> > ---
> >  drivers/staging/typec/Kconfig       |  11 +
> >  drivers/staging/typec/Makefile      |   1 +
> >  drivers/staging/typec/typec_wcove.c | 684 
> > ++++++++++++++++++++++++++++++++++++
> >  drivers/usb/typec/Makefile          |   1 -
> >  drivers/usb/typec/typec_wcove.c     | 377 --------------------
> >  5 files changed, 696 insertions(+), 378 deletions(-)
> >  create mode 100644 drivers/staging/typec/typec_wcove.c
> >  delete mode 100644 drivers/usb/typec/typec_wcove.c
> > 
> > Hi,
> > 
> > I would like to register also this driver with tcpm, but since tcpm is
> > in staging, can we move the driver to staging like in this patch?
> 
> How about spending the time to get the code out of staging instead?  I
> don't like adding new features to staging drivers, instead, I want to
> see people working to fix what we have before adding new stuff...

I agree that we need to get tcpm out of staging, and soon (I was not
expecting it to go staging at all, but as Guenter said, it's good to
have it in), but I also want to make sure that nobody, instead of
spending the time to get tcpm out of staging, starts preparing their
own USB PD state machines. That is really what has been happening, and
will continue to happen unless we do something.

So I want to make sure tcpm is being developed instead of something
else, and that is the reason I want to hook up also our whiskeycove
driver with it already at this point. I hope that makes sense.


Thanks,

-- 
heikki
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to