public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Wolfram Sang <wsa@kernel.org>
Cc: Bough Chen <haibo.chen@nxp.com>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	"lars@metafoo.de" <lars@metafoo.de>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"pmeerw@pmeerw.net" <pmeerw@pmeerw.net>,
	dl-linux-imx <linux-imx@nxp.com>
Subject: Re: [PATCH] iio: accel: mma8452: remove the reset operation during driver probe
Date: Sat, 4 Jun 2022 17:16:57 +0100	[thread overview]
Message-ID: <20220604171657.78eb7927@jic23-huawei> (raw)
In-Reply-To: <YhfBZv7msnpvDVEs@ninjato>

On Thu, 24 Feb 2022 18:33:26 +0100
Wolfram Sang <wsa@kernel.org> wrote:

> > > Wolfram is there a standard way to work around missing ACK in cases like
> > > this?  Would just ignoring the return value be fine or are their i2c masters
> > > that will get stuck if they don't get the expected ack?  
> 
> Did I get this right: the reset procedures terminates the ACK and STOP?
> And the client expects a new START condition for communication?
> 

@Bough Chen,

I'm assuming this is still an issue for you?  If so can you reply to
Wolfram so we can hopefully move this forwards.

Found this because it's still listed as needing an action in the IIO
patchwork.

Thanks,

Jonathan

  reply	other threads:[~2022-06-04 16:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-22  4:45 [PATCH] iio: accel: mma8452: remove the reset operation during driver probe haibo.chen
2022-02-22 16:43 ` Jonathan Cameron
2022-02-24 14:31   ` Bough Chen
2022-02-24 17:33     ` Wolfram Sang
2022-06-04 16:16       ` Jonathan Cameron [this message]
2022-06-06  2:06         ` Bough Chen
2022-06-15 11:26         ` Bough Chen

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=20220604171657.78eb7927@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=haibo.chen@nxp.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=pmeerw@pmeerw.net \
    --cc=wsa@kernel.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