mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Craig Hesling <craig@hesling.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org, sboyd@kernel.org
Subject: Re: [PATCH] USB: serial: simple: add OWON HDS200 series oscilloscope support
Date: Wed, 16 Apr 2025 08:35:30 +0200	[thread overview]
Message-ID: <Z_9PssdqzDrAmgUb@hovoldconsulting.com> (raw)
In-Reply-To: <20250408232703.954945-1-craig@hesling.com>

On Tue, Apr 08, 2025 at 04:27:03PM -0700, Craig Hesling wrote:
> Add serial support for OWON HDS200 series oscilloscopes and likely
> many other pieces of OWON test equipment.
> 
> OWON HDS200 series devices host two USB endpoints, designed to
> facilitate bidirectional SCPI. SCPI is a predominately ASCII text
> protocol for test/measurement equipment. Having a serial/tty interface
> for these devices lowers the barrier to entry for anyone trying to
> write programs to communicate with them.
> 
> The following shows the USB descriptor for the OWON HDS272S running
> firmware V5.7.1:
> 
> Bus 001 Device 068: ID 5345:1234 Owon PDS6062T Oscilloscope

> OWON appears to be using the same USB Vendor and Product ID for many
> of their oscilloscopes. Looking at the discussion about the USB
> vendor/product ID, in the link bellow, suggests that this VID/PID is
> shared with VDS, SDS, PDS, and now the HDS series oscilloscopes.
> Available documentation for these devices seems to indicate that all
> use a similar SCPI protocol, some with RS232 options. It is likely that
> this same simple serial setup would work correctly for them all.
> 
> Link: https://usb-ids.gowdy.us/read/UD/5345/1234
> Signed-off-by: Craig Hesling <craig@hesling.com>

Thanks for the patch. Now applied.

Johan

  reply	other threads:[~2025-04-16  6:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08 23:27 Craig Hesling
2025-04-16  6:35 ` Johan Hovold [this message]
2025-04-16 21:56   ` Craig Hesling

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=Z_9PssdqzDrAmgUb@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=craig@hesling.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sboyd@kernel.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

all inboxes | Powered by JetHome®