All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Support Opensource <support.opensource@diasemi.com>,
	 Lee Jones <lee@kernel.org>,
	linux-kernel@vger.kernel.org,
	 Jens Kehne <jens.kehne@agilent.com>
Subject: Re: (subset) [PATCH] mfd: da9063: Split chip variant reading in two bus transactions
Date: Tue, 02 Sep 2025 09:13:36 +0100	[thread overview]
Message-ID: <175680081626.2184374.7626461049800985884.b4-ty@kernel.org> (raw)
In-Reply-To: <20250804133754.3496718-1-jens.kehne@agilent.com>

On Mon, 04 Aug 2025 15:37:54 +0200, Jens Kehne wrote:
> We observed the initial probe of the da9063 failing in
> da9063_get_device_type in about 30% of boots on a Xilinx ZynqMP based
> board. The problem originates in da9063_i2c_blockreg_read, which uses
> a single bus transaction to turn the register page and then read a
> register. On the bus, this should translate to a write to register 0,
> followed by a read to the target register, separated by a repeated
> start. However, we found that after the write to register 0, the
> controller sometimes continues directly with the register address of
> the read request, without sending the chip address or a repeated start
> in between, which makes the read request invalid.
> 
> [...]

Applied, thanks!

[1/1] mfd: da9063: Split chip variant reading in two bus transactions
      commit: a0d1178ea4778fc1eb1691a97619ecdb8a3bda13

--
Lee Jones [李琼斯]


      reply	other threads:[~2025-09-02  8:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-04 13:37 [PATCH] mfd: da9063: Split chip variant reading in two bus transactions Jens Kehne
2025-09-02  8:13 ` Lee Jones [this message]

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=175680081626.2184374.7626461049800985884.b4-ty@kernel.org \
    --to=lee@kernel.org \
    --cc=jens.kehne@agilent.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=support.opensource@diasemi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.