kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: gregkh@linuxfoundation.org (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [usb-serial] Support for console read from usb serial driver
Date: Thu, 1 Feb 2018 21:15:09 +0100	[thread overview]
Message-ID: <20180201201509.GA24756@kroah.com> (raw)
In-Reply-To: <CABXF_AB8Z1J+s=mqkn012XqZC6xYEhZQ8QUQj=EZ1QAiTnAXyA@mail.gmail.com>

On Thu, Feb 01, 2018 at 11:52:18PM +0530, Ivid Suvarna wrote:
> Hi All,
> 
> I was going through usb serial driver console related source code
> (drivers/usb/serial/console.c) in linux kernel and came across
> "usb_console_write" function and was wondering if any usb serial
> convertor drivers were using this function? If so any pointers on how
> it is being used?

Yes, they all can use it.  Have you tried?

> Also can we implement something like "usb_console_read" which can be
> useful for interactive debugging like in kgdb. I saw kgdb using
> something like "poll_get_char and poll_put_char". I found them in most
> of serial drivers like 8250 and so on.

kgdb needs to run without interrupts enabled, which is impossible for
USB normally.  There has been external patches to get USB to work for
debugging, but that might have only been for simple keyboards.

> I am using pl2303 usb to serial convertor for getting a serial
> console. Is there any way to implement something like usb_console_read
> in usb serial drivers? Can you guys give me some pointers on this.

It should "just work" today for you.  What did you try that was not
working properly?

thanks,

greg k-h

      reply	other threads:[~2018-02-01 20:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-01 18:22 [usb-serial] Support for console read from usb serial driver Ivid Suvarna
2018-02-01 20:15 ` Greg KH [this message]

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=20180201201509.GA24756@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /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).