public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Visweswara Tanuku <quic_vtanuku@quicinc.com>
Cc: konrad.dybcio@linaro.org, bartosz.golaszewski@linaro.org,
	linux-kernel@vger.kernel.org, quic_vnivarth@quicinc.com,
	nicolas.dechesne@linaro.org, srinivas.kandagatla@linaro.org,
	vinod.koul@linaro.org, quic_eberman@quicinc.com,
	quic_satyap@quicinc.com
Subject: Re: [RESEND] soc: qcom-geni-se: Update Tx and Rx fifo depth based on QUP HW version
Date: Mon, 6 Feb 2023 13:38:56 +0100	[thread overview]
Message-ID: <Y+D04FIti7yejya+@kroah.com> (raw)
In-Reply-To: <20230206122215.22090-1-quic_vtanuku@quicinc.com>

On Mon, Feb 06, 2023 at 04:22:15AM -0800, Visweswara Tanuku wrote:
> >From QUP HW Version 3.10 and above the Tx and Rx
> fifo depth bits are increased to 23:16 bits from
> 21:16 bits in SE_HW_PARAM registers accomodating
> 256bytes of fifo depth.
> 
> Updated geni_se_get_tx_fifo_depth and
> geni_se_get_rx_fifo_depth to retrieve right fifo
> depth based on QUP HW version.
> 
> Signed-off-by: Visweswara Tanuku <quic_vtanuku@quicinc.com>
> ---
>  include/linux/qcom-geni-se.h | 42 ++++++++++++++++++++++++++++++------
>  1 file changed, 36 insertions(+), 6 deletions(-)

Why is this a RESEND?  What was wrong with the first version?

confused,

greg k-h

  reply	other threads:[~2023-02-06 12:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06 12:22 [RESEND] soc: qcom-geni-se: Update Tx and Rx fifo depth based on QUP HW version Visweswara Tanuku
2023-02-06 12:38 ` Greg KH [this message]
     [not found]   ` <ca31f247-0297-7582-c16f-a85453872ca4@quicinc.com>
2023-02-06 18:09     ` Greg KH
     [not found]       ` <0afc0752-1a4e-be3a-e9bd-0f56243d5e41@quicinc.com>
2023-02-08 11:57         ` Greg KH

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=Y+D04FIti7yejya+@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.dechesne@linaro.org \
    --cc=quic_eberman@quicinc.com \
    --cc=quic_satyap@quicinc.com \
    --cc=quic_vnivarth@quicinc.com \
    --cc=quic_vtanuku@quicinc.com \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=vinod.koul@linaro.org \
    /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