mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeffrey Hugo <quic_jhugo@quicinc.com>
To: Hemant Kumar <hemantk@codeaurora.org>,
	Bhaumik Bhatt <bbhatt@codeaurora.org>,
	<manivannan.sadhasivam@linaro.org>
Cc: <linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<loic.poulain@linaro.org>
Subject: Re: [PATCH v1 1/2] bus: mhi: core: Bail on writing register fields if read fails
Date: Thu, 19 Aug 2021 08:05:26 -0600	[thread overview]
Message-ID: <48d494d8-1323-87fd-4a95-c1714bfa2ae9@quicinc.com> (raw)
In-Reply-To: <45fbfe24-38eb-82f0-7134-a04854269247@codeaurora.org>

On 8/18/2021 7:40 PM, Hemant Kumar wrote:
> 
> 
> On 8/18/2021 4:50 PM, Bhaumik Bhatt wrote:
>> Helper API to write register fields relies on successful reads
>> of the register/address prior to the write. Bail out if a failure
>> is seen when reading the register before the actual write is
>> performed.
>>
>> Signed-off-by: Bhaumik Bhatt <bbhatt@codeaurora.org>
> Reviewed-by: Hemant Kumar <hemantk@codeaurora.org>
> 

Reviewed-by: Jeffrey Hugo <quic_jhugo@quicinc.com>

  reply	other threads:[~2021-08-19 14:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-18 23:50 [PATCH v1 0/2] MHI MMIO register write updates Bhaumik Bhatt
2021-08-18 23:50 ` [PATCH v1 1/2] bus: mhi: core: Bail on writing register fields if read fails Bhaumik Bhatt
2021-08-19  1:40   ` Hemant Kumar
2021-08-19 14:05     ` Jeffrey Hugo [this message]
2021-08-19  2:50   ` kernel test robot
2021-08-19 17:02   ` Manivannan Sadhasivam
2021-08-18 23:50 ` [PATCH v1 2/2] bus: mhi: core: Optimize and update MMIO register write method Bhaumik Bhatt
2021-08-19  1:41   ` Hemant Kumar
2021-08-19 14:05     ` Jeffrey Hugo
2021-08-19 17:03   ` Manivannan Sadhasivam

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=48d494d8-1323-87fd-4a95-c1714bfa2ae9@quicinc.com \
    --to=quic_jhugo@quicinc.com \
    --cc=bbhatt@codeaurora.org \
    --cc=hemantk@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loic.poulain@linaro.org \
    --cc=manivannan.sadhasivam@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

all inboxes | Powered by JetHome®