From: tony@atomide•com (Tony Lindgren)
To: linux-arm-kernel@lists•infradead.org
Subject: Vibrations on Droid 4?
Date: Mon, 16 Jul 2018 00:59:26 -0700 [thread overview]
Message-ID: <20180716075926.GU99251@atomide.com> (raw)
In-Reply-To: <20180715201729.GB19675@amd>
* Pavel Machek <pavel@ucw•cz> [180715 20:20]:
> Yep, so I have two patches that make the device appear, but vibrations
> still do not work for me.
>
> a) any ideas how to debug that / get them to work?
Hmm no new ideas except I wonder if there is also some other
regression with the timer pdata not being passed properly now.
> b) do you want the patches anyway?
Yes for things that are obviously broken it makes sense.
Thanks,
Tony
next prev parent reply other threads:[~2018-07-16 7:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 8:15 Vibrations on Droid 4? Pavel Machek
2018-07-09 21:49 ` Sebastian Reichel
2018-07-09 22:02 ` Pavel Machek
2018-07-10 10:11 ` Sebastian Reichel
2018-07-10 13:30 ` Pavel Machek
2018-07-10 16:11 ` Sebastian Reichel
2018-07-11 8:02 ` Pavel Machek
2018-07-11 13:27 ` Tony Lindgren
2018-07-11 14:25 ` Sebastian Reichel
2018-07-16 7:10 ` [PATCH] dts/droid4: fix dts w.r.t. pwm Pavel Machek
2018-07-16 10:11 ` Sebastian Reichel
2018-07-17 6:48 ` Tony Lindgren
2018-07-16 7:13 ` [PATCH] pwm-omap: handle timers not ready in probe Pavel Machek
2018-07-16 7:57 ` Tony Lindgren
2018-07-16 8:37 ` Pavel Machek
2018-07-16 15:47 ` David Rivshin
2018-07-15 20:17 ` Vibrations on Droid 4? Pavel Machek
2018-07-16 7:59 ` Tony Lindgren [this message]
2018-08-01 18:58 ` Pavel Machek
2018-08-02 11:07 ` Sebastian Reichel
2018-08-08 17:09 ` Pavel Machek
2018-08-01 20:26 ` Pavel Machek
2018-08-01 20:28 ` [PATCH] fix vibrations on Droid 4 Pavel Machek
2018-08-02 10:55 ` Sebastian Reichel
2018-08-17 14:26 ` Tony Lindgren
2018-07-11 8:25 ` Vibrations on Droid 4? Pavel Machek
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=20180716075926.GU99251@atomide.com \
--to=tony@atomide$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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