From: Greg KH <gregkh@linuxfoundation.org>
To: Mathias Nyman <mathias.nyman@linux.intel.com>
Cc: Prabhat Chand Pandey <prabhat.chand.pandey@intel.com>,
linux-usb@vger.kernel.org, mathias.nyman@intel.com,
rajaram.regupathy@intel.com, abhilash.k.v@intel.com,
m.balaji@intel.com
Subject: Re: [PATCH 4/5] usb: xhci: dbc: Add a dbc raw driver to provide a raw interface on DbC
Date: Mon, 10 Jun 2019 16:16:07 +0200 [thread overview]
Message-ID: <20190610141607.GA5937@kroah.com> (raw)
In-Reply-To: <af51b855-4ee4-9bc2-6484-b8c4d897f503@linux.intel.com>
On Mon, Jun 10, 2019 at 04:53:51PM +0300, Mathias Nyman wrote:
> On 7.6.2019 17.21, Greg KH wrote:
> > On Fri, Jun 07, 2019 at 12:03:05PM +0530, Prabhat Chand Pandey wrote:
> > > From: Abhilash K V <abhilash.k.v@intel.com>
> > >
> > > This patch provides a raw device interface on xhci Debug capability.
> >
> > What is a "raw device"?
> >
> > > This abstracts dbc functionality to user space inorder to facilitate
> > > various frameworks to utilize xhci debug capability.
> >
> > I do not understand this sentance at all. Please provide a lot more
> > information.
> >
> > > It helps to render the target as an usb debug class device on host and
> > > establish an usb connection by providing two bulk endpoints.
> >
> > provide bulk endpoints where? To send data where? This is very
> > confusing and does not make any sense to me...
> >
> >
> > >
> > > [don't dynamically allocate tiny space for name only -Mathias]
> > > Signed-off-by: Rajaram Regupathy <rajaram.regupathy@intel.com>
> > > Signed-off-by: Prabhat Chand Pandey <prabhat.chand.pandey@intel.com>
> > > Signed-off-by: Abhilash K V <abhilash.k.v@intel.com>
> > > Acked-by: Mathias Nyman <mathias.nyman@linux.intel.com>
> > > ---
> ...
> >
> > So you have a new char device, with a undocumented and unknown format of
> > data flowing across it to the device. How in the world are we supposed
> > to use this thing? Where is it documented? What does it do? How can
> > you use it?
> >
> > I don't mean to be so harsh here, but come on people, this stuff needs a
> > lot more background documentation, information, and explaination as to
> > exactly why in the world we need any of this, and what it even does!
> >
> > Also, you need to fix the code, it doesn't work as pointed out in a few
> > places :)
> >
>
> Thanks for going through this.
> It's now clear this is far from ready.
> I need to re-evaluate my position on this, not just the code and the documentation,
> but the usefulness of it all.
What is this even supposed to be used for? What is the application for
it? I couldn't determine that at all, what am I missing?
thanks,
greg k-h
next prev parent reply other threads:[~2019-06-10 14:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 6:33 [PATCH 0/5] usb: xhci: dbc: make modular and add RAW interface Prabhat Chand Pandey
2019-06-07 6:33 ` [PATCH 1/5] usb: xhci: dbc: make DbC modular, introducing dbc_function structure Prabhat Chand Pandey
2019-06-07 14:02 ` Greg KH
2019-06-07 6:33 ` [PATCH 2/5] usb: xhci: dbc: DbC TTY driver to use new interface Prabhat Chand Pandey
2019-06-07 14:06 ` Greg KH
2019-06-07 6:33 ` [PATCH 3/5] usb: xhci: dbc: Provide sysfs option to configure dbc descriptors Prabhat Chand Pandey
2019-06-07 14:10 ` Greg KH
2019-06-07 6:33 ` [PATCH 4/5] usb: xhci: dbc: Add a dbc raw driver to provide a raw interface on DbC Prabhat Chand Pandey
2019-06-07 14:21 ` Greg KH
2019-06-10 13:53 ` Mathias Nyman
2019-06-10 14:16 ` Greg KH [this message]
2019-06-11 9:29 ` Regupathy, Rajaram
2019-06-11 9:52 ` Greg KH
2019-06-11 12:17 ` Regupathy, Rajaram
2019-06-11 12:34 ` Greg KH
2019-06-12 8:49 ` Regupathy, Rajaram
2019-06-12 10:54 ` Greg KH
2019-06-13 12:33 ` Felipe Balbi
2019-06-13 13:02 ` Greg KH
2019-06-07 6:33 ` [PATCH 5/5] usb: xhci: dbc: Document describe about dbc raw interface Prabhat Chand Pandey
2019-06-07 14:25 ` Greg KH
2019-06-07 13:59 ` [PATCH 0/5] usb: xhci: dbc: make modular and add RAW interface Greg KH
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=20190610141607.GA5937@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=abhilash.k.v@intel.com \
--cc=linux-usb@vger.kernel.org \
--cc=m.balaji@intel.com \
--cc=mathias.nyman@intel.com \
--cc=mathias.nyman@linux.intel.com \
--cc=prabhat.chand.pandey@intel.com \
--cc=rajaram.regupathy@intel.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;
as well as URLs for NNTP newsgroup(s).