From: Jiri Pirko <jiri@resnulli.us>
To: Michal Michalik <michal.michalik@intel.com>
Cc: netdev@vger.kernel.org, vadim.fedorenko@linux.dev,
arkadiusz.kubalewski@intel.com, jonathan.lemon@gmail.com,
pabeni@redhat.com, poros@redhat.com, milena.olech@intel.com,
mschmidt@redhat.com, linux-clk@vger.kernel.org,
bvanassche@acm.org, kuba@kernel.org, davem@davemloft.net,
edumazet@google.com
Subject: Re: [PATCH RFC net-next v2 0/2] selftests/dpll: DPLL subsystem integration tests
Date: Tue, 31 Oct 2023 10:47:00 +0100 [thread overview]
Message-ID: <ZUDNFHlO4GtA/UAh@nanopsycho> (raw)
In-Reply-To: <20231030165326.24453-1-michal.michalik@intel.com>
Mon, Oct 30, 2023 at 05:53:24PM CET, michal.michalik@intel.com wrote:
>The recently merged common DPLL interface discussed on a newsletter[1]
"newsletter"? Sounds a bit odd to me :)
>is introducing new, complex subsystem which requires proper integration
>testing - this patch adds core for such framework, as well as the
"Patchset" perhaps? Also, what do you mean by "core"? The sentence
sounds a bit weird to me.
>initial test cases. Framework does not require neither any special
>hardware nor any special system architecture.
>
>To properly test the DPLL subsystem this patch adds fake DPLL devices and it's
For patch desctiption, please stay within 72cols.
Also, "it's" is most probably wrong in this sentence.
>pins implementation to netdevsim. Creating netdevsim devices and adding ports
>to it register new DPLL devices and pins. First port of each netdevsim device
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This sentence does not make
sense to me. Pehaps rephrase a bit?
>acts as a entitiy which registers two DPLL devices: EEC and PPS DPLLs. First
typo: "entitiy"
>port also register the common pins: PPS and GNSS. Additionally each port
>register also RCLK (recovered clock) pin for itself. That allow us to check
>mutliple scenarios which might be problematic in real implementations (like
>different ordering etc.)
>
>Patch adds few helper scripts, which are:
>1) tools/testing/selftests/dpll/run_dpll_tests.sh
Please make this part of
tools/testing/selftests/drivers/net/netdevsim/
No special threat of dpll needed.
> Script is checking for all dependencies, creates temporary
> environment, installs required libraries and run all tests - can be
> used standalone
>2) tools/testing/selftests/dpll/ynlfamilyhandler.py˙
> Library for easier ynl use in the pytest framework - can be used
> standalone
>
>[1] https://lore.kernel.org/netdev/169494842736.21621.10730860855645661664.git-patchwork-notify@kernel.org/
>
>Changelog:
>v1 -> v2:
>- moved from separate module to implementation in netdevsim
>
>Michal Michalik (2):
> netdevsim: implement DPLL for subsystem selftests
> selftests/dpll: add DPLL system integration selftests
>
> drivers/net/Kconfig | 1 +
> drivers/net/netdevsim/Makefile | 2 +-
> drivers/net/netdevsim/dpll.c | 438 +++++++++++++++++++++++
> drivers/net/netdevsim/dpll.h | 81 +++++
> drivers/net/netdevsim/netdev.c | 20 ++
> drivers/net/netdevsim/netdevsim.h | 4 +
> tools/testing/selftests/Makefile | 1 +
> tools/testing/selftests/dpll/Makefile | 8 +
> tools/testing/selftests/dpll/__init__.py | 0
> tools/testing/selftests/dpll/config | 2 +
> tools/testing/selftests/dpll/consts.py | 34 ++
> tools/testing/selftests/dpll/dpll_utils.py | 109 ++++++
> tools/testing/selftests/dpll/requirements.txt | 3 +
> tools/testing/selftests/dpll/run_dpll_tests.sh | 75 ++++
> tools/testing/selftests/dpll/test_dpll.py | 414 +++++++++++++++++++++
> tools/testing/selftests/dpll/ynlfamilyhandler.py | 49 +++
> 16 files changed, 1240 insertions(+), 1 deletion(-)
> create mode 100644 drivers/net/netdevsim/dpll.c
> create mode 100644 drivers/net/netdevsim/dpll.h
> create mode 100644 tools/testing/selftests/dpll/Makefile
> create mode 100644 tools/testing/selftests/dpll/__init__.py
> create mode 100644 tools/testing/selftests/dpll/config
> create mode 100644 tools/testing/selftests/dpll/consts.py
> create mode 100644 tools/testing/selftests/dpll/dpll_utils.py
> create mode 100644 tools/testing/selftests/dpll/requirements.txt
> create mode 100755 tools/testing/selftests/dpll/run_dpll_tests.sh
> create mode 100644 tools/testing/selftests/dpll/test_dpll.py
> create mode 100644 tools/testing/selftests/dpll/ynlfamilyhandler.py
>
>--
>2.9.5
>
>base-commit: 55c900477f5b3897d9038446f72a281cae0efd86
next prev parent reply other threads:[~2023-10-31 9:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 16:53 [PATCH RFC net-next v2 0/2] selftests/dpll: DPLL subsystem integration tests Michal Michalik
2023-10-30 16:53 ` [PATCH RFC net-next v2 1/2] netdevsim: implement DPLL for subsystem selftests Michal Michalik
2023-10-31 10:59 ` Jiri Pirko
2023-11-03 17:45 ` Michalik, Michal
2023-11-04 7:53 ` Jiri Pirko
2023-10-30 16:53 ` [PATCH RFC net-next v2 2/2] selftests/dpll: add DPLL system integration selftests Michal Michalik
2023-10-31 9:47 ` Jiri Pirko [this message]
2023-11-03 17:45 ` [PATCH RFC net-next v2 0/2] selftests/dpll: DPLL subsystem integration tests Michalik, Michal
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=ZUDNFHlO4GtA/UAh@nanopsycho \
--to=jiri@resnulli.us \
--cc=arkadiusz.kubalewski@intel.com \
--cc=bvanassche@acm.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=michal.michalik@intel.com \
--cc=milena.olech@intel.com \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=poros@redhat.com \
--cc=vadim.fedorenko@linux.dev \
/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