From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: guido@kiener-muenchen.de
Cc: linux-usb@vger.kernel.org, guido.kiener@rohde-schwarz.com,
pankaj.adhikari@ni.com, steve_bayless@keysight.com,
dpenkler@gmail.com
Subject: [04/12] usb: usbtmc: Add ioctls for trigger, EOM bit and TermChar
Date: Fri, 18 May 2018 14:29:02 +0200 [thread overview]
Message-ID: <20180518122902.GA7866@kroah.com> (raw)
On Fri, May 18, 2018 at 12:08:16PM +0000, guido@kiener-muenchen.de wrote:
>
> Zitat von Greg KH <gregkh@linuxfoundation.org>:
>
> > On Thu, May 17, 2018 at 07:03:28PM +0200, Guido Kiener wrote:
> > > - add USBTMC488_IOCTL_TRIGGER to send TRIGGER Bulk-OUT header
> > > according to Subclass USB488 Specification
> > >
> > > The usbtmc trigger command is equivalent to the IEEE 488 GET (Group
> > > Execute Trigger) action. While the "*TRG" command can be sent as
> > > data to perform the same operation, in some situations an instrument
> > > will be busy and unable to process the data immediately in which
> > > case the USBTMC488_IOCTL_TRIGGER can be used to trigger the
> > > instrument with lower latency.
> > >
> > > - add USBTMC_IOCTL_EOM_ENABLE to specify EOM bit for next write()
> > > call. Sets Bit 0 of field 'bmTransferAttributes' of DEV_DEP_MSG_OUT
> > > Bulk-OUT Header.
> > >
> > > Allows fine grained control over end of message handling on a
> > > per file descriptor basis.
> > >
> > > - add USBTMC_IOCTL_CONFIG_TERMCHAR to control TermChar handling
> > > for next read(). Controls field 'TermChar' and Bit 1 of field
> > > 'bmTransferAttributes' of REQUEST_DEV_DEP_MSG_IN BULK-OUT header.
> > >
> > > Allows enabling/disabling of terminating a read on reception of
> > > term_char individually for each read request.
> >
> > Why isn't this 3 patches? Please only do "one thing per patch".
>
> I just thought it is clearly arranged. Please let me know when you
> want to see a breakup of other patches as well.
I only got this far in the patch series and I stopped. As you know this
has to be broken up, please do that and we can iterate from there.
Worse case, I take the first few patches and you redo the later ones,
that's a very common process.
> However I would be happy when I could save some extra work here.
> In the middle of next week I start my holiday.
No rush on my end, there's no deadlines in kernel development, send them
when you have them ready :)
thanks,
greg k-h
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-05-18 12:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 12:29 Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-24 12:41 [04/12] usb: usbtmc: Add ioctls for trigger, EOM bit and TermChar Guido Kiener
2018-05-23 11:58 Oliver Neukum
2018-05-18 12:08 Guido Kiener
2018-05-17 17:03 Guido Kiener
2018-05-17 16:21 Greg Kroah-Hartman
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=20180518122902.GA7866@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dpenkler@gmail.com \
--cc=guido.kiener@rohde-schwarz.com \
--cc=guido@kiener-muenchen.de \
--cc=linux-usb@vger.kernel.org \
--cc=pankaj.adhikari@ni.com \
--cc=steve_bayless@keysight.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.