From: Pavel Pisa <pisa@cmp.felk.cvut.cz>
To: "Marc Kleine-Budde" <mkl@pengutronix.de>
Cc: Matej Vasilevski <matej.vasilevski@seznam.cz>,
Ondrej Ille <ondrej.ille@gmail.com>,
Wolfgang Grandegger <wg@grandegger.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
linux-can@vger.kernel.org
Subject: Re: [PATCH v5 2/4] can: ctucanfd: add HW timestamps to RX and error CAN frames
Date: Mon, 24 Oct 2022 13:42:29 +0200 [thread overview]
Message-ID: <202210241342.29170.pisa@cmp.felk.cvut.cz> (raw)
In-Reply-To: <20221017121122.kt6adqz4dtqc2sy5@pengutronix.de>
Hello Marc,
On Monday 17 of October 2022 14:11:22 Marc Kleine-Budde wrote:
> On 16.10.2022 23:54:48, Pavel Pisa wrote:
> [...]
>
> > I hope/expect that it is not problem to call clk_prepare_enable twice
> > on same reference when the clocks are the same. As I read the code the
> > state is counted. If it is a problem then some if has to be put there
> > when the core and timestamp clock are the same.
>
> The clock prepare and enable are counting. If you call then twice, you
> have to call disable and unprepare twice, too, to shut it down. This is
> widely used in the kernel, e.g. if the same clock is passed to several
> IP cores.
Thanks for confirmation of my understanding.
As to move formward, is the referenced Matej Vasilevski's
series acceptable by you or do you see some problems still?
I have ACKed this patch, I consider it as functional
for mainline and good base for our further testing
and development.
Should I ACK others as well or Reviewed-by: Rob Herring
is enough for deice tree?
The last one is exactly reaction to your comment and the
documentation is evident.
Best wishes,
Pavel
--
Pavel Pisa
phone: +420 603531357
e-mail: pisa@cmp.felk.cvut.cz
Department of Control Engineering FEE CVUT
Karlovo namesti 13, 121 35, Prague 2
university: http://control.fel.cvut.cz/
personal: http://cmp.felk.cvut.cz/~pisa
projects: https://www.openhub.net/accounts/ppisa
CAN related:http://canbus.pages.fel.cvut.cz/
RISC-V education: https://comparch.edu.cvut.cz/
Open Technologies Research Education and Exchange Services
https://gitlab.fel.cvut.cz/otrees/org/-/wikis/home
next prev parent reply other threads:[~2022-10-24 21:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 6:25 [PATCH v5 0/4] can: ctucanfd: hardware rx timestamps reporting Matej Vasilevski
2022-10-12 6:25 ` [PATCH v5 1/4] dt-bindings: can: ctucanfd: add another clock for HW timestamping Matej Vasilevski
2022-10-12 16:21 ` Rob Herring
2022-10-12 6:25 ` [PATCH v5 2/4] can: ctucanfd: add HW timestamps to RX and error CAN frames Matej Vasilevski
2022-10-16 21:54 ` Pavel Pisa
2022-10-17 12:11 ` Marc Kleine-Budde
2022-10-24 11:42 ` Pavel Pisa [this message]
2022-10-24 20:02 ` Marc Kleine-Budde
2022-10-25 22:22 ` Matej Vasilevski
2022-10-26 7:15 ` Marc Kleine-Budde
2022-10-25 8:18 ` Marc Kleine-Budde
2022-10-25 9:25 ` Marc Kleine-Budde
2022-10-12 6:25 ` [PATCH v5 3/4] doc: ctucanfd: RX frames timestamping for platform devices Matej Vasilevski
2022-10-12 6:25 ` [PATCH v5 4/4] can: ctucanfd: remove __maybe_unused from suspend/resume callbacks Matej Vasilevski
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=202210241342.29170.pisa@cmp.felk.cvut.cz \
--to=pisa@cmp.felk.cvut.cz \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=matej.vasilevski@seznam.cz \
--cc=mkl@pengutronix.de \
--cc=ondrej.ille@gmail.com \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=wg@grandegger.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