From: Simon Horman <horms@kernel.org>
To: Min Li <min.li.xe@renesas.com>
Cc: Paolo Abeni <pabeni@redhat.com>, Min Li <lnimi@hotmail.com>,
"richardcochran@gmail.com" <richardcochran@gmail.com>,
"lee@kernel.org" <lee@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v6 1/6] ptp: clockmatrix: support 32-bit address space
Date: Thu, 7 Dec 2023 11:10:55 +0000 [thread overview]
Message-ID: <20231207111055.GF50400@kernel.org> (raw)
In-Reply-To: <OS3PR01MB6593B50F4C5BF3687EE3FA97BA84A@OS3PR01MB6593.jpnprd01.prod.outlook.com>
On Wed, Dec 06, 2023 at 04:29:09PM +0000, Min Li wrote:
> > >
> > > Hi Min Li,
> > >
> > > My understanding of Paolo's review of v5 was that it would be cleaner to:
> > >
> > > 1. Leave the type of the module parameter as u16 2. Update the type of
> > > the regaddr parameter to u32
> >
> > [almost over the air conflict here ;) ]
> >
> > I think the module parameter as u32 is needed, as later macro definitions
> > will leverage that.
Yes, sorry. I got things muddled up there.
> > > And...
> > >
> > > ... avoid the need for changes like the two above.
> >
> > This part is correct/what I meant ;)
> >
>
> Hi Paolo/Simon
>
> Thanks for your reviews. Ideally, I would want to maintain regaddr as u16 since for clockmatrix addressing, it is only the lower 8bit of the whole 32bit address while module is upper 24bit. On the other hand, for some simple cases, where only one register in a module, their addresses are defined by module only without regaddr such as sync_ctrl0/1
>
> Overall, I still want to differentiate between module and regaddr and don't wanna mix them up.
My reading is that this patch reverses the usage of module and regaddr.
F.e. the following hunk:
@@ -553,11 +554,11 @@ static int _sync_pll_output(struct idtcm *idtcm,
val = SYNCTRL1_MASTER_SYNC_RST;
/* Place master sync in reset */
err = idtcm_write(idtcm, 0, sync_ctrl1, &val, sizeof(val));
err = idtcm_write(idtcm, sync_ctrl1, 0, &val, sizeof(val));
if (err)
return err;
err = idtcm_write(idtcm, 0, sync_ctrl0, &sync_src, sizeof(sync_src));
err = idtcm_write(idtcm, sync_ctrl0, 0, &sync_src, sizeof(sync_src));
if (err)
return err;
If that is really intended I think it needs to be explained, or possibly
a separate patch.
next prev parent reply other threads:[~2023-12-07 11:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 18:46 [PATCH net-next v6 1/6] ptp: clockmatrix: support 32-bit address space Min Li
2023-12-05 9:06 ` Paolo Abeni
2023-12-05 9:24 ` Simon Horman
2023-12-05 9:28 ` Paolo Abeni
2023-12-06 16:29 ` Min Li
2023-12-07 11:10 ` Simon Horman [this message]
2023-12-13 21:04 ` Min Li
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=20231207111055.GF50400@kernel.org \
--to=horms@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lnimi@hotmail.com \
--cc=min.li.xe@renesas.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).