From: Xu Yilun <yilun.xu@intel.com>
To: "Wu, Hao" <hao.wu@intel.com>
Cc: "mdf@kernel.org" <mdf@kernel.org>,
"linux-fpga@vger.kernel.org" <linux-fpga@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"trix@redhat.com" <trix@redhat.com>,
"lgoncalv@redhat.com" <lgoncalv@redhat.com>,
Matthew Gerlach <matthew.gerlach@linux.intel.com>,
"Weight, Russell H" <russell.h.weight@intel.com>
Subject: Re: [PATCH v3 4/4] fpga: dfl: add support for N3000 nios private feature
Date: Wed, 5 Aug 2020 16:35:04 +0800 [thread overview]
Message-ID: <20200805083504.GA20262@yilunxu-OptiPlex-7050> (raw)
In-Reply-To: <DM6PR11MB38196B703EA0772783466AA9854A0@DM6PR11MB3819.namprd11.prod.outlook.com>
Thanks for your quick response, I'm OK with most changes. Some comments
inline.
On Tue, Aug 04, 2020 at 08:56:12PM +0800, Wu, Hao wrote:
> > Subject: [PATCH v3 4/4] fpga: dfl: add support for N3000 nios private feature
>
> > +#define NIOS_INIT0x1000
> > +#define NIOS_INIT_DONEBIT(0)
> > +#define NIOS_INIT_STARTBIT(1)
> > +/* Mode for PKVL A, link 0, the same below */
> > +#define REQ_FEC_MODE_A0_MSKGENMASK(9, 8)
> > +#define REQ_FEC_MODE_A1_MSKGENMASK(11, 10)
> > +#define REQ_FEC_MODE_A2_MSKGENMASK(13, 12)
> > +#define REQ_FEC_MODE_A3_MSKGENMASK(15, 14)
> > +#define REQ_FEC_MODE_B0_MSKGENMASK(17, 16)
> > +#define REQ_FEC_MODE_B1_MSKGENMASK(19, 18)
> > +#define REQ_FEC_MODE_B2_MSKGENMASK(21, 20)
> > +#define REQ_FEC_MODE_B3_MSKGENMASK(23, 22)
> > +#define REQ_FEC_MODE_NO0x0
> > +#define REQ_FEC_MODE_KR0x1
> > +#define REQ_FEC_MODE_RS0x2
>
> What does REQ mean?
It's the abbreviation of REQUEST, on spec these fields names
REQUEST_FEC_MODE_X_X
> > +/* ns is the abbreviation of nios_spi */
> > +static int ns_bus_poll_stat_timeout(void __iomem *base, u64 *v)
>
> Why adding "bus" here? I just see it's polling on register bits, right?
> It's a little confusing on ns_bus.
It is the polling for regmap read/write, the regmap is also called
regbus, so I name ns_bus here.
I could change the name, do you think there is confusing also for
ns_bus_reg_read & ns_bus_reg_write?
Thanks,
Yilun.
next prev parent reply other threads:[~2020-08-05 8:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 7:05 [PATCH v3 0/4] Modularization of DFL private feature drivers Xu Yilun
2020-08-04 7:05 ` [PATCH v3 1/4] fpga: dfl: change data type of feature id to u16 Xu Yilun
2020-08-05 9:13 ` Wu, Hao
2020-08-04 7:05 ` [PATCH v3 2/4] fpga: dfl: map feature mmio resources in their own feature drivers Xu Yilun
2020-08-05 12:15 ` Wu, Hao
2020-08-06 2:43 ` Xu Yilun
2020-08-04 7:05 ` [PATCH v3 3/4] fpga: dfl: create a dfl bus type to support DFL devices Xu Yilun
2020-08-05 10:29 ` Wu, Hao
2020-08-06 6:02 ` Xu Yilun
2020-08-06 7:11 ` Wu, Hao
2020-08-06 8:50 ` Xu Yilun
2020-08-04 7:05 ` [PATCH v3 4/4] fpga: dfl: add support for N3000 nios private feature Xu Yilun
2020-08-04 12:56 ` Wu, Hao
2020-08-05 8:35 ` Xu Yilun [this message]
2020-08-05 9:11 ` Wu, Hao
[not found] ` <b5d4157b-1bdf-445c-58a7-abd2f485a5ff@redhat.com>
2020-08-05 8:36 ` Xu Yilun
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=20200805083504.GA20262@yilunxu-OptiPlex-7050 \
--to=yilun.xu@intel.com \
--cc=hao.wu@intel.com \
--cc=lgoncalv@redhat.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.gerlach@linux.intel.com \
--cc=mdf@kernel.org \
--cc=russell.h.weight@intel.com \
--cc=trix@redhat.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®