public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Antoniu Miclaus <antoniu.miclaus@analog.com>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
	"Michael Hennerich" <Michael.Hennerich@analog.com>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Olivier Moysan" <olivier.moysan@foss.st.com>,
	"Mark Brown" <broonie@kernel.org>,
	"Sebastian Reichel" <sebastian.reichel@collabora.com>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org
Subject: Re: [PATCH v4 1/5] spi: allow ancillary devices to share parent's chip selects
Date: Tue, 24 Feb 2026 12:09:28 +0200	[thread overview]
Message-ID: <aZ142CVjMQ8Dypnb@smile.fi.intel.com> (raw)
In-Reply-To: <20260223162110.156746-2-antoniu.miclaus@analog.com>

On Mon, Feb 23, 2026 at 06:21:00PM +0200, Antoniu Miclaus wrote:
> When registering an ancillary SPI device, the current code flags a chip
> select conflict with the parent device. This happens because the
> ancillary device intentionally uses one of the parent's chip selects,
> but __spi_add_device() checks against all existing devices including
> the parent.
> 
> Allow this by passing the parent device pointer to __spi_add_device()
> and skipping the conflict check when the existing device is the parent.

Isn't this already applied?

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2026-02-24 10:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23 16:20 [PATCH v4 0/5] iio: adc: ad4080: add support for AD4880 dual-channel ADC Antoniu Miclaus
2026-02-23 16:21 ` [PATCH v4 1/5] spi: allow ancillary devices to share parent's chip selects Antoniu Miclaus
2026-02-24 10:09   ` Andy Shevchenko [this message]
2026-02-24 11:12     ` Miclaus, Antoniu
2026-02-24 11:24       ` Andy Shevchenko
2026-02-24 11:41         ` Miclaus, Antoniu
2026-02-23 16:21 ` [PATCH v4 2/5] spi: add devm_spi_new_ancillary_device() Antoniu Miclaus
2026-02-23 16:21 ` [PATCH v4 3/5] iio: backend: add devm_iio_backend_get_by_index() Antoniu Miclaus
2026-02-24 10:16   ` Andy Shevchenko
2026-02-28 19:05   ` Jonathan Cameron
2026-02-23 16:21 ` [PATCH v4 4/5] dt-bindings: iio: adc: ad4080: add AD4880 support Antoniu Miclaus
2026-02-23 16:21 ` [PATCH v4 5/5] iio: adc: ad4080: add support for AD4880 dual-channel ADC Antoniu Miclaus
2026-02-24 10:24   ` Andy Shevchenko
2026-02-28 19:10   ` Jonathan Cameron
2026-02-25 19:09 ` (subset) [PATCH v4 0/5] " Mark Brown
2026-02-28 19:00   ` Jonathan Cameron
2026-02-28 21:35 ` Mark Brown

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=aZ142CVjMQ8Dypnb@smile.fi.intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy@kernel.org \
    --cc=antoniu.miclaus@analog.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=olivier.moysan@foss.st.com \
    --cc=robh@kernel.org \
    --cc=sebastian.reichel@collabora.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