From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: "linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: Regarding clock event driver testing
Date: Fri, 25 Nov 2022 11:51:02 +0100 [thread overview]
Message-ID: <Y4CeFrBzfUkNiV3d@ninjato> (raw)
In-Reply-To: <OS0PR01MB5922C23B892D938AD1675C9C860E9@OS0PR01MB5922.jpnprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 793 bytes --]
Hi Biju,
> On RZ/V2M, we have 16 timer channels. First channel we planned to use it as clock source
> And remaining 15 channels as clock event devices. I used clocksource-switch to verify
> Clocksource functionality. But currently I do not know how to test the clock event?
I would love to help, but sadly I can't. CMT/TMU haven't been changed in
ages. So, when I upstream them for new SoCs, I test basic/slightly
advanced functionality with 'clocksource-switch' and assume the rest has
been tested before. I didn't test clocksource events. Magnus seems to
have started something, but AFAIU it does the same as your devmem tests:
https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=&submitter=19&state=*&q=cmt&archive=&delegate=
Sorry I can't be of more help.
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-11-25 10:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 9:07 Regarding clock event driver testing Biju Das
2022-11-25 10:51 ` Wolfram Sang [this message]
2022-11-25 11:40 ` Biju Das
2022-11-28 9:02 ` Biju Das
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=Y4CeFrBzfUkNiV3d@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=linux-renesas-soc@vger.kernel.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 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.