From: Takashi Iwai <tiwai@suse.de>
To: Baojun Xu <baojun.xu@ti.com>
Cc: <tiwai@suse.de>, <hansg@kernel.org>,
<ilpo.jarvinen@linux.intel.com>, <broonie@kernel.org>,
<andriy.shevchenko@linux.intel.com>, <shenghao-ding@ti.com>,
<13916275206@139.com>, <platform-driver-x86@vger.kernel.org>,
<linux-sound@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<letitia.tsai@hp.com>, <bill.yu@canonical.com>,
<pin-hao.huang@hp.com>
Subject: Re: [PATCH v1] ALSA: hda/tas2781: Fix device-0 reset issue and handle -EXDEV in block data processing
Date: Wed, 10 Jun 2026 09:24:46 +0200 [thread overview]
Message-ID: <87v7bq6eo1.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260609105253.19510-1-baojun.xu@ti.com>
On Tue, 09 Jun 2026 12:52:53 +0200,
Baojun Xu wrote:
>
> Fix reset for device-0: In older projects (e.g., Merino), the hardware
> reset pin for the first SPI device (device-0) is ineffective, causing
> initialization failures. Added a software reset sequence for device-0
> to ensure proper initialization.
>
> Handle -EXDEV correctly: When processing block data, if the data does
> not belong to the current SPI device, the driver returned -EXDEV.
> This error code is now ignored to allow the driver to continue iterating
> through the block data and correctly calculate the total block size.
>
> Signed-off-by: Baojun Xu <baojun.xu@ti.com>
Applied to for-next branch now. Thanks.
Takashi
prev parent reply other threads:[~2026-06-10 7:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 10:52 [PATCH v1] ALSA: hda/tas2781: Fix device-0 reset issue and handle -EXDEV in block data processing Baojun Xu
2026-06-10 7:24 ` Takashi Iwai [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=87v7bq6eo1.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=13916275206@139.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=baojun.xu@ti.com \
--cc=bill.yu@canonical.com \
--cc=broonie@kernel.org \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=letitia.tsai@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=pin-hao.huang@hp.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=shenghao-ding@ti.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