From: Greg T <greg.iforce@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: |Question] iforce Boeder Force Feedback Wheel
Date: Mon, 4 Jul 2022 20:41:36 +0200 [thread overview]
Message-ID: <CAKEH-65f_8771=qiZXpytrTT4J0TMRHCsg4KCcphhDDMw__wug@mail.gmail.com> (raw)
In-Reply-To: <CAKEH-64QJ3HbPwNhPy1T2YKR19w5XfDBiFhWD2M1oQqkHfs70A@mail.gmail.com>
2022-07-04 4:19 GMT+02:00, Greg T <greg.iforce@gmail.com>:
> Call Trace:
> <TASK>
> _raw_spin_lock_irqsave+0x41/0x50
> uart_write+0x69/0x1e0
> serport_serio_write+0x2b/0x40 [serport]
> iforce_serio_xmit+0xa8/0x1a0 [iforce_serio]
> serport_ldisc_write_wakeup+0x59/0x70 [serport]
I've found this in tty_ldisc.h:
* @write_wakeup: [DRV] ``void ()(struct tty_struct *tty)``
*
* This function is called by the low-level tty driver to signal that line
* discpline should try to send more characters to the low-level driver
* for transmission. If the line discpline does not have any more data to
* send, it can just return. If the line discipline does have some data to
* send, please arise a tasklet or workqueue to do the real data transfer.
* Do not send data in this hook, it may lead to a deadlock.
Does iforce-serio.c have a maintainer? It looks to me that
iforce_serio_write_wakeup should not call iforce_serio_xmit in it.
prev parent reply other threads:[~2022-07-04 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <495ce212-addc-8ab1-a851-4fd5f6c5c8d9@gmail.com>
2022-07-03 5:11 ` |Question] iforce Boeder Force Feedback Wheel Randy Dunlap
2022-07-04 2:19 ` Greg T
2022-07-04 18:41 ` Greg T [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='CAKEH-65f_8771=qiZXpytrTT4J0TMRHCsg4KCcphhDDMw__wug@mail.gmail.com' \
--to=greg.iforce@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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).