From: Shijith Thotton <sthotton@marvell.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
Sunil Kovvuri Goutham <sgoutham@marvell.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] octeontx2-af: cn10k: devlink params to configure TIM
Date: Mon, 29 Nov 2021 08:15:14 +0000 [thread overview]
Message-ID: <PH0PR18MB44259826C271BCDF11BBB86CD9669@PH0PR18MB4425.namprd18.prod.outlook.com> (raw)
>> Added devlink parameters to configure the source clock of TIM block.
>> Supported clocks are TENNS, GPIOS, GTI, PTP, SYNC, BTS, EXT_MIO and
>> EXT_GTI.
>>
>> To adjust a given clock, the required delta can be written to the
>> corresponding tim_adjust_<clock> parameter and tim_adjust_timers
>> parameter can be used to trigger the adjustment. tim_capture_<clock>
>> parameter can be used to verify the adjusted values for a clock.
>>
>> Example using tenns clock source:
>> To adjust a clock source
>> # devlink dev param set pci/0002:01:00.0 name tim_adjust_tenns \
>> value "1000" cmode runtime
>>
>> To trigger adjustment
>> # devlink dev param set pci/0002:01:00.0 name tim_adjust_timers \
>> value 1 cmode runtime
>
>PTP subsystem exists.
TIM is a hardware block in Octeon TX2 DPU, which is used to generate events
like timeout (used in packet processing). TIM input needs to be configured with a
clock source for its working, but TIM does not act as a clock source. Supported
clocks for input are TENNS, GPIOS, GTI, PTP, SYNC, BTS and MIO. Devlink
parameters added in this patch are to configure TIM and won't be changing the
clock sources.
We won't be able to use PTP subsystem here as the changes are specific to TIM.
next reply other threads:[~2021-11-29 8:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 8:15 Shijith Thotton [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-24 5:08 [PATCH net-next] octeontx2-af: cn10k: devlink params to configure TIM Shijith Thotton
2021-11-25 0:48 ` Jakub Kicinski
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=PH0PR18MB44259826C271BCDF11BBB86CD9669@PH0PR18MB4425.namprd18.prod.outlook.com \
--to=sthotton@marvell.com \
--cc=davem@davemloft.net \
--cc=jerinj@marvell.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sgoutham@marvell.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.