From: <min.li.xe@renesas.com>
To: <richardcochran@gmail.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Min Li <min.li.xe@renesas.com>
Subject: [PATCH v2 net-next 0/5] ptp_clockmatrix bug fix and improvement
Date: Tue, 17 Nov 2020 11:05:57 -0500 [thread overview]
Message-ID: <1605629162-31876-1-git-send-email-min.li.xe@renesas.com> (raw)
From: Min Li <min.li.xe@renesas.com>
This patch series is aiming at submitting the latest bug fixes and code
improvements of PHC driver for Renesas CLOCKMATRIX timing card. The code
has been thouroughly tested in both customer labs and Renesas internal
lab using the latest linuxptp program on Xilinx ZCU102 platform.
Changes since v1:
-Only strcpy 15 characters to leave 1 space for '\0'
Min Li (5):
ptp: clockmatrix: bug fix for idtcm_strverscmp
ptp: clockmatrix: reset device and check BOOT_STATUS
ptp: clockmatrix: remove 5 second delay before entering write phase
mode
ptp: clockmatrix: Fix non-zero phase_adj is lost after snap
ptp: clockmatrix: deprecate firmware older than 4.8.7
drivers/ptp/idt8a340_reg.h | 1 +
drivers/ptp/ptp_clockmatrix.c | 477 ++++++++++++++++++++++++++++++++----------
drivers/ptp/ptp_clockmatrix.h | 24 ++-
3 files changed, 384 insertions(+), 118 deletions(-)
--
2.7.4
next reply other threads:[~2020-11-17 16:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 16:05 min.li.xe [this message]
2020-11-17 16:05 ` [PATCH v2 net-next 1/5] ptp: clockmatrix: bug fix for idtcm_strverscmp min.li.xe
2020-11-17 16:05 ` [PATCH v2 net-next 2/5] ptp: clockmatrix: reset device and check BOOT_STATUS min.li.xe
2020-11-17 16:06 ` [PATCH v2 net-next 3/5] ptp: clockmatrix: remove 5 second delay before entering write phase mode min.li.xe
2020-11-17 16:06 ` [PATCH v2 net-next 4/5] ptp: clockmatrix: Fix non-zero phase_adj is lost after snap min.li.xe
2020-11-17 16:06 ` [PATCH v2 net-next 5/5] ptp: clockmatrix: deprecate firmware older than 4.8.7 min.li.xe
2020-11-17 20:44 ` kernel test robot
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=1605629162-31876-1-git-send-email-min.li.xe@renesas.com \
--to=min.li.xe@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@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®