From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/4] clocksource: rockchip: Make the driver more compatible
Date: Mon, 2 Nov 2015 18:28:38 +0100 [thread overview]
Message-ID: <56379D46.1000402@linaro.org> (raw)
In-Reply-To: <21587719.mnFBFBzBeI@phil>
On 10/31/2015 12:47 AM, Heiko Stuebner wrote:
> Hi Daniel,
>
> Am Freitag, 30. Oktober 2015, 11:42:29 schrieb Daniel Lezcano:
>> On 10/30/2015 04:43 AM, Caesar Wang wrote:
>>> Hi Daniel,
>>>
>>> ? 2015?10?01? 03:14, Heiko St?bner ??:
>>>> Hi Daniel,
>>>>
>>>> Am Dienstag, 29. September 2015, 06:18:03 schrieb Daniel Lezcano:
>>>>> On 09/25/2015 04:14 AM, Caesar Wang wrote:
>>>>>> Build the arm64 SoCs (e.g.: RK3368) on Rockchip platform,
>>>>>> There are some failure with build up on timer driver for rockchip.
>>>>>>
>>>>>> Says:
>>>>>> /tmp/ccdAnNy5.s:47: Error: missing immediate expression at operand
>>>>>> 1 --
>>>>>> `dsb`
>>>>>> ...
>>>>>>
>>>>>> The problem was different semantics of dsb on btw arm32 and arm64,
>>>>>> Here we can convert the dsb with insteading of dsb(sy).The "sy" param
>>>>>> is the default which you are allow to omit, so on arm32 dsb()and
>>>>>> dsb(sy)
>>>>>> are the same.
>>>>>>
>>>>>> Signed-off-by: Caesar Wang <wxt@rock-chips.com>
>>>>> Acked-by: Daniel Lezcano <daniel.lezcano@linaro.org>
>>>> as you have "just" Acked these patches, I guess you are expecting them
>>>> to go
>>>> through the same tree as the devicetree changes, right?
>>>
>>> I'm wonder if someone will apply this series patchs but the wait.:-)
>>> In fact, I'm no sure that the Acked is really meaning.:-
>>
>> Yes, by acking the patch I say I am ok with it and I agree it can go
>> through another tree.
>
> although I guess the two clocksource changes could very well just go
> through your tree. dsb() -> dsb(sy) is supposed to be equal and the second
> one is just cosmetics. The Kconfig and dts changes need to wait in any case
> for 4.5 ... but I guess that may be true for the clocksource changes as well?
Heiko, Caesar,
I am wondering if the dsb() is really necessary. Is it possible you test
the timer by removing this instruction ? Otherwise I will have to setup
my board again and it will take awhile.
--
<http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2015-11-02 17:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 2:14 [PATCH v2 0/4] Support the timer on RK3368 SoC Caesar Wang
2015-09-25 2:14 ` [PATCH v2 1/4] clocksource: rockchip: Make the driver more compatible Caesar Wang
2015-09-29 4:18 ` Daniel Lezcano
2015-09-30 19:14 ` Heiko Stübner
2015-10-30 3:43 ` Caesar Wang
2015-10-30 10:42 ` Daniel Lezcano
2015-10-30 23:47 ` Heiko Stuebner
2015-10-31 13:04 ` Daniel Lezcano
2015-11-02 17:28 ` Daniel Lezcano [this message]
2015-11-03 2:00 ` Caesar Wang
2015-11-03 8:32 ` Daniel Lezcano
2015-11-03 9:59 ` Caesar Wang
2015-09-25 2:14 ` [PATCH v2 2/4] clocksource: rockchip: trivial: Make the driver more readability Caesar Wang
2015-09-29 4:18 ` Daniel Lezcano
2015-09-25 2:14 ` [PATCH v2 3/4] arm64: Enable the timer on Rockchip architecture Caesar Wang
2016-01-25 13:51 ` Heiko Stübner
2015-09-25 2:14 ` [PATCH v2 4/4] arm64: dts: rockchip: Add the needed timer for RK3368 SoC Caesar Wang
2015-12-13 0:47 ` Heiko Stübner
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=56379D46.1000402@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.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).