public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Zaidman <michael.zaidman@gmail.com>
To: Daniel Beer <daniel.beer@igorinstitute.com>
Cc: Christina Quast <contact@christina-quast.de>,
	linux-serial@vger.kernel.org, ilpo.jarvinen@linux.intel.com,
	johan@kernel.org, gregkh@linuxfoundation.org,
	David Lamparter <equinox@diac24.net>,
	Jiri Kosina <jikos@kernel.org>,
	Michael Zaidman <michael.zaidman@gmail.com>
Subject: Re: [PATCH v4 RESEND] hid-ft260: Add serial driver
Date: Sun, 21 Jan 2024 11:12:54 +0200	[thread overview]
Message-ID: <ZazgFniD3qXGG1cY@michael-VirtualBox> (raw)
In-Reply-To: <ZaxFkPY3W/5SFwh6@fermat.nev>

On Sun, Jan 21, 2024 at 11:13:36AM +1300, Daniel Beer wrote:
> On Sat, Jan 20, 2024 at 08:41:28PM +0200, Michael Zaidman wrote:
> > Hi Daniel and Christina,
> > 
> > My concern with the implemented workaround is that sending a dummy report
> > every 4.8 seconds eliminates the chip's power save mode functionality.
> > 
> > I did more testing and figured out that the baud rates 4800 and below work
> > fine with power saving mode and do not require this workaround.
> > 
> > So, I modified the code, making it dependent on the baud rate in this commit:
> > https://github.com/MichaelZaidman/hid-ft260/commit/b5a2ad68c7cebbaaba0aa1675ae376f2895e19aa
> > 
> > 
> > Another improvement is not to activate the wakeup workaround if power
> > saving mode is not enabled in EEPROM.
> > https://github.com/MichaelZaidman/hid-ft260/commit/0a41f3f3a4c664edc3bb90718807f2e62fe6d375
> > 
> > For UART testing, I sent files via picocom opened on ttyUSB0 (ch340 USB
> > dongle device) connected to ft260 UART, receiving and displaying the
> > trafic in screen manager utility.
> > 
> > --Michael
> 
> Hi Michael,
> 
> That sounds like a good idea to me. Are you planning to submit your
> improved version from here?
> 
> I don't have any FT260 hardware with me any more, so there's
> unfortunately not much I can do now to help, aside from answering
> questions.
> 
> Cheers,
> Daniel
> 

Yeah, I mean to do more testing, and then I will submit a new patch set
based on your work.

--Michael


  reply	other threads:[~2024-01-21  9:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-18  9:31 [PATCH v4 RESEND] hid-ft260: Add serial driver Christina Quast
2023-12-28 11:50 ` Christina Quast
2024-01-02 21:42   ` Michael Zaidman
2024-01-16 21:44     ` Michael Zaidman
2024-01-16 21:34 ` Michael Zaidman
2024-01-16 21:43   ` Daniel Beer
2024-01-17 20:43     ` Michael Zaidman
2024-01-20 18:41       ` Michael Zaidman
2024-01-20 22:13         ` Daniel Beer
2024-01-21  9:12           ` Michael Zaidman [this message]
2024-01-28 22:07             ` Michael Zaidman
2024-01-31  6:28               ` Daniel Beer
2024-01-31 15:48                 ` Michael Zaidman
     [not found]                   ` <041c7445-fd59-4615-bb9a-7958b93113e8@christina-quast.de>
2024-02-02  9:04                     ` Michael Zaidman
2024-02-10 22:03                       ` Michael Zaidman
2024-02-01 11:07   ` Christina Quast

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=ZazgFniD3qXGG1cY@michael-VirtualBox \
    --to=michael.zaidman@gmail.com \
    --cc=contact@christina-quast.de \
    --cc=daniel.beer@igorinstitute.com \
    --cc=equinox@diac24.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jikos@kernel.org \
    --cc=johan@kernel.org \
    --cc=linux-serial@vger.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