From: Joe Perches <joe@perches.com>
To: Varun Prakash <varun@chelsio.com>, bart.vanassche@sandisk.com
Cc: target-devel@vger.kernel.org, netdev@vger.kernel.org,
indranil@chelsio.com
Subject: Re: [PATCH] cxgbit: use T6 specific macro to set force bit
Date: Tue, 24 Jan 2017 13:11:40 -0800 [thread overview]
Message-ID: <1485292300.12563.41.camel@perches.com> (raw)
In-Reply-To: <1485257822-729-1-git-send-email-varun@chelsio.com>
On Tue, 2017-01-24 at 17:07 +0530, Varun Prakash wrote:
> For T6 adapters use T6 specific macro to set
> force bit.
[]
> diff --git a/drivers/net/ethernet/chelsio/cxgb4/t4_msg.h b/drivers/net/ethernet/chelsio/cxgb4/t4_msg.h
[]
> @@ -1349,6 +1349,10 @@ struct cpl_tx_data {
> #define TX_FORCE_S 13
> #define TX_FORCE_V(x) ((x) << TX_FORCE_S)
>
> +#define T6_TX_FORCE_S 20
> +#define T6_TX_FORCE_V(x) ((x) << T6_TX_FORCE_S)
> +#define T6_TX_FORCE_F T6_TX_FORCE_V(1U)
> +
> enum {
> ULP_TX_MEM_READ = 2,
> ULP_TX_MEM_WRITE = 3,
> diff --git a/drivers/target/iscsi/cxgbit/cxgbit_target.c b/drivers/target/iscsi/cxgbit/cxgbit_target.c
[]
> @@ -162,12 +162,14 @@ cxgbit_tx_data_wr(struct cxgbit_sock *csk, struct sk_buff *skb, u32 dlen,
> u32 len, u32 credits, u32 compl)
> {
> struct fw_ofld_tx_data_wr *req;
> + const struct cxgb4_lld_info *lldi = &csk->com.cdev->lldi;
> u32 submode = cxgbit_skcb_submode(skb);
> u32 wr_ulp_mode = 0;
> u32 hdr_size = sizeof(*req);
> u32 opcode = FW_OFLD_TX_DATA_WR;
> u32 immlen = 0;
> - u32 force = TX_FORCE_V(!submode);
> + u32 force = is_t5(lldi->adapter_type) ? TX_FORCE_V(!submode) :
> + T6_TX_FORCE_F;
Perhaps it'd be better to add a is_t6() mechanism so this
is written in the positive rather than the negative.
next prev parent reply other threads:[~2017-01-24 21:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 11:37 [PATCH] cxgbit: use T6 specific macro to set force bit Varun Prakash
2017-01-24 20:26 ` David Miller
2017-01-25 6:21 ` Varun Prakash
2017-01-24 21:11 ` Joe Perches [this message]
2017-01-25 6:38 ` Varun Prakash
2017-01-25 16:06 ` Joe Perches
2017-01-25 23:01 ` Bart Van Assche
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=1485292300.12563.41.camel@perches.com \
--to=joe@perches.com \
--cc=bart.vanassche@sandisk.com \
--cc=indranil@chelsio.com \
--cc=netdev@vger.kernel.org \
--cc=target-devel@vger.kernel.org \
--cc=varun@chelsio.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).