From: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Sebastian Reichel <sre@kernel.org>, Pavel Machel <pavel@ucw.cz>,
Timo Kokkonen <timo.t.kokkonen@iki.fi>,
linux-media@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Neil Armstrong <narmstrong@baylibre.com>
Subject: Re: [PATCH 0/2] Fix ir-rx51 by using PWM pdata
Date: Sat, 30 Apr 2016 20:52:11 +0300 [thread overview]
Message-ID: <5724F0CB.6060807@gmail.com> (raw)
In-Reply-To: <20160428212748.GI5995@atomide.com>
Hi,
On 29.04.2016 00:27, Tony Lindgren wrote:
> * Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com> [160428 14:21]:
>>
>> I didn't test legacy boot, as I don't really see any value of doing it now
>> the end of the legacy boot is near, the driver does not function correctly,
>> however the patchset at least allows for the driver to be build and we have
>> something to improve on. And I am going to send a patch that fixes the
>> problem with omap_dm_timer_request_specific(). So, for both patches, you may
>> add:
>>
>> Tested-by: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
>
> OK thanks.
>
> Mauro, do the driver changes look OK to you?
>
> If so, I could queue the driver too for v4.7 because of the
> dependency with your ack. Or I can provide you an immutable
> branch with just the pdata changes against v4.6-rc1 if you
> prefer that.
>
In the meanwhile I was able to make the driver functional (on top of the
$subject series) - for that purpose I had to fix dmtimer.c - it turns
out that PM runtime get()/put() is called in almost every function
exported by dmtimer, which in turn slows down IR transmission to 4-5s
instead of 0.5s. I also replaced GPT9 dmtimer with PWM framework API
(pwm-omap-dmtimer needs a patch) and implemented some DT support.
Now, how shall I proceed with those - wait for the $subject series to be
accepted or post the patches now?
Tony, I was unable to find the tree on kernel.org your patches are in.
Which tree to use to base my patches on?
Thanks,
Ivo
WARNING: multiple messages have this Message-ID (diff)
From: ivo.g.dimitrov.75@gmail.com (Ivaylo Dimitrov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Fix ir-rx51 by using PWM pdata
Date: Sat, 30 Apr 2016 20:52:11 +0300 [thread overview]
Message-ID: <5724F0CB.6060807@gmail.com> (raw)
In-Reply-To: <20160428212748.GI5995@atomide.com>
Hi,
On 29.04.2016 00:27, Tony Lindgren wrote:
> * Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com> [160428 14:21]:
>>
>> I didn't test legacy boot, as I don't really see any value of doing it now
>> the end of the legacy boot is near, the driver does not function correctly,
>> however the patchset at least allows for the driver to be build and we have
>> something to improve on. And I am going to send a patch that fixes the
>> problem with omap_dm_timer_request_specific(). So, for both patches, you may
>> add:
>>
>> Tested-by: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
>
> OK thanks.
>
> Mauro, do the driver changes look OK to you?
>
> If so, I could queue the driver too for v4.7 because of the
> dependency with your ack. Or I can provide you an immutable
> branch with just the pdata changes against v4.6-rc1 if you
> prefer that.
>
In the meanwhile I was able to make the driver functional (on top of the
$subject series) - for that purpose I had to fix dmtimer.c - it turns
out that PM runtime get()/put() is called in almost every function
exported by dmtimer, which in turn slows down IR transmission to 4-5s
instead of 0.5s. I also replaced GPT9 dmtimer with PWM framework API
(pwm-omap-dmtimer needs a patch) and implemented some DT support.
Now, how shall I proceed with those - wait for the $subject series to be
accepted or post the patches now?
Tony, I was unable to find the tree on kernel.org your patches are in.
Which tree to use to base my patches on?
Thanks,
Ivo
next prev parent reply other threads:[~2016-04-30 17:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 23:51 [PATCH 0/2] Fix ir-rx51 by using PWM pdata Tony Lindgren
2016-04-26 23:51 ` Tony Lindgren
2016-04-26 23:51 ` [PATCH 1/2] ARM: OMAP2+: Add more functions to pwm pdata for ir-rx51 Tony Lindgren
2016-04-26 23:51 ` Tony Lindgren
2016-04-26 23:51 ` [PATCH 2/2] [media] ir-rx51: Fix build after multiarch changes broke it Tony Lindgren
2016-04-26 23:51 ` Tony Lindgren
2016-04-27 11:18 ` Pavel Machek
2016-04-27 11:18 ` Pavel Machek
2016-04-28 19:38 ` Ivaylo Dimitrov
2016-04-28 19:38 ` Ivaylo Dimitrov
2016-04-28 20:22 ` Tony Lindgren
2016-04-28 20:22 ` Tony Lindgren
2016-04-28 20:43 ` Ivaylo Dimitrov
2016-04-28 20:43 ` Ivaylo Dimitrov
2016-04-28 20:55 ` Tony Lindgren
2016-04-28 20:55 ` Tony Lindgren
2016-04-28 21:19 ` [PATCH 0/2] Fix ir-rx51 by using PWM pdata Ivaylo Dimitrov
2016-04-28 21:19 ` Ivaylo Dimitrov
2016-04-28 21:27 ` Tony Lindgren
2016-04-28 21:27 ` Tony Lindgren
2016-04-30 17:52 ` Ivaylo Dimitrov [this message]
2016-04-30 17:52 ` Ivaylo Dimitrov
2016-05-05 17:11 ` Tony Lindgren
2016-05-05 17:11 ` Tony Lindgren
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=5724F0CB.6060807@gmail.com \
--to=ivo.g.dimitrov.75@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=narmstrong@baylibre.com \
--cc=pavel@ucw.cz \
--cc=sre@kernel.org \
--cc=timo.t.kokkonen@iki.fi \
--cc=tony@atomide.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.