mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Heiko Stuebner <heiko@sntech.de>,
	Sebastian Reichel <sebastian.reichel@collabora.com>,
	Sugar Zhang <sugar.zhang@rock-chips.com>,
	Shreeya Patel <shreeya.patel@collabora.com>,
	Kever Yang <kever.yang@rock-chips.com>,
	Johan Jonker <jbx6244@gmail.com>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, kernel@collabora.com
Subject: Re: [PATCH v3 0/3] Enable rk3588 timer support
Date: Sat, 22 Apr 2023 18:15:51 +0300	[thread overview]
Message-ID: <80d23bb9-b55a-57c5-4aa1-d29a919b04ae@collabora.com> (raw)
In-Reply-To: <CAEwRq=o71XMoj6_QU-mKrrrBqz80=C0g4fMwejv7fN-vAop89w@mail.gmail.com>

On 4/22/23 16:17, Vincent Legoll wrote:
> Hello,
> 
> On Wed, Apr 19, 2023 at 6:13 PM Cristian Ciocaltea
> <cristian.ciocaltea@collabora.com> wrote:
>> This patchset enables Rockchip RK3588/RK3588S SoC timer support.
>> While here, it also handles a minor DT binding issue related to RK3288.
> 
> I tested this on a QuartzPro64 dev board, I applied your series top of my tree:
> Collabora's rk3588 + some DT patches to add support for the qp64 board.
> 
> Here is the output from the commands you told me to try:
> 
> bash-5.1# grep rk_timer /sys/bus/clockevents/devices/*/current_device
> /sys/bus/clockevents/devices/broadcast/current_device:rk_timer
> 
> bash-5.1# grep -B3 -A14 'Device: rk_timer' /proc/timer_list
> 
> Tick Device: mode:     1
> Broadcast device
> Clock Event Device: rk_timer
>  max_delta_ns:   178956969070
>  min_delta_ns:   1000
>  mult:           51539608
>  shift:          31
>  mode:           3
>  next_event:     150944000000 nsecs
>  set_next_event: rk_timer_set_next_event
>  shutdown:       rk_timer_shutdown
>  periodic:       rk_timer_set_periodic
>  event_handler:  tick_handle_oneshot_broadcast
> 
>  retries:        0
> 
> tick_broadcast_mask: ff
> 
> bash-5.1# head -1 /proc/interrupts ; grep rk_timer /proc/interrupts;
> sleep 10; grep rk_timer /proc/interrupts
>            CPU0       CPU1       CPU2       CPU3       CPU4       CPU5
>       CPU6       CPU7
>  25:        742        210         52         49       2197       1640
>       1089       2341     GICv3 321 Level     rk_timer
>  25:        754        222         52         49       2252       1727
>       1146       2404     GICv3 321 Level     rk_timer
> 
> So it looks like this is working.
> 
> Thanks for your work.
> 
> You can add my:
> 
> Tested-by: Vincent Legoll <vincent.legoll@gmail.com>

Thanks for taking the time to test this!

Regards,
Cristian

  reply	other threads:[~2023-04-22 15:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-19 18:13 Cristian Ciocaltea
2023-04-19 18:13 ` [PATCH v3 1/3] dt-bindings: timer: rockchip: Drop superfluous rk3288 compatible Cristian Ciocaltea
2023-04-21  7:23   ` Krzysztof Kozlowski
2023-04-26  9:12   ` [tip: timers/core] " tip-bot2 for Cristian Ciocaltea
2023-04-19 18:13 ` [PATCH v3 2/3] dt-bindings: timer: rockchip: Add rk3588 compatible Cristian Ciocaltea
2023-04-26  9:12   ` [tip: timers/core] " tip-bot2 for Cristian Ciocaltea
2023-04-19 18:13 ` [PATCH v3 3/3] arm64: dts: rockchip: Add rk3588 timer Cristian Ciocaltea
2023-04-22 13:17 ` [PATCH v3 0/3] Enable rk3588 timer support Vincent Legoll
2023-04-22 15:15   ` Cristian Ciocaltea [this message]
2023-04-22 15:42     ` Vincent Legoll
2023-04-26 10:57 ` (subset) " Heiko Stuebner

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=80d23bb9-b55a-57c5-4aa1-d29a919b04ae@collabora.com \
    --to=cristian.ciocaltea@collabora.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=jbx6244@gmail.com \
    --cc=kernel@collabora.com \
    --cc=kever.yang@rock-chips.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=sebastian.reichel@collabora.com \
    --cc=shreeya.patel@collabora.com \
    --cc=sugar.zhang@rock-chips.com \
    --cc=tglx@linutronix.de \
    --cc=vincent.legoll@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®