From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
Jai Luthra <jai.luthra@ideasonboard.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Romain Gantois <romain.gantois@bootlin.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: Re: linux-next: manual merge of the v4l-dvb tree with the i2c tree
Date: Thu, 29 May 2025 12:49:29 +1000 [thread overview]
Message-ID: <20250529124929.5217c6d9@canb.auug.org.au> (raw)
In-Reply-To: <20250428113052.38cf10da@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 5170 bytes --]
Hi all,
On Mon, 28 Apr 2025 11:30:52 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> On Mon, 28 Apr 2025 11:22:00 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > On Mon, 28 Apr 2025 10:49:05 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > >
> > > Today's linux-next merge of the v4l-dvb tree got a conflict in:
> > >
> > > drivers/media/i2c/ds90ub960.c
> > >
> > > between commits:
> > >
> > > 3ec29d51b546 ("media: i2c: ds90ub960: Protect alias_use_mask with a mutex")
> > > 818bd489f137 ("i2c: use client addresses directly in ATR interface")
> > >
> > > from the i2c tree and commits:
> > >
> > > 24868501a744 ("media: i2c: ds90ub9xx: Add err parameter to read/write funcs")
> > > 2ca499384e98 ("media: i2c: ds90ub960: Add RX port iteration support")
> > >
> > > from the v4l-dvb tree.
> > >
> > > I fixed it up (see below) and can carry the fix as necessary. This
> > > is now fixed as far as linux-next is concerned, but any non trivial
> > > conflicts should be mentioned to your upstream maintainer when your tree
> > > is submitted for merging. You may also want to consider cooperating
> > > with the maintainer of the conflicting tree to minimise any particularly
> > > complex conflicts.
> >
> > The actual resolution is below ...
>
> I hit the wrong key :-( Resolution below.
> --
> Cheers,
> Stephen Rothwell
>
> diff --cc drivers/media/i2c/ds90ub960.c
> index 5a4d5de110bd,1877eb735cc7..000000000000
> --- a/drivers/media/i2c/ds90ub960.c
> +++ b/drivers/media/i2c/ds90ub960.c
> @@@ -1056,11 -1271,10 +1274,12 @@@ static int ub960_atr_attach_addr(struc
> struct ub960_rxport *rxport = priv->rxports[chan_id];
> struct device *dev = &priv->client->dev;
> unsigned int reg_idx;
> + int ret = 0;
>
> - for (reg_idx = 0; reg_idx < ARRAY_SIZE(rxport->aliased_clients); reg_idx++) {
> - if (!rxport->aliased_clients[reg_idx])
> + guard(mutex)(&rxport->aliased_addrs_lock);
> +
> + for (reg_idx = 0; reg_idx < ARRAY_SIZE(rxport->aliased_addrs); reg_idx++) {
> + if (!rxport->aliased_addrs[reg_idx])
> break;
> }
>
> @@@ -1069,15 -1283,18 +1288,18 @@@
> return -EADDRNOTAVAIL;
> }
>
> - rxport->aliased_clients[reg_idx] = client;
> + rxport->aliased_addrs[reg_idx] = addr;
>
> ub960_rxport_write(priv, chan_id, UB960_RR_SLAVE_ID(reg_idx),
> - addr << 1);
> - client->addr << 1, &ret);
> ++ addr << 1, &ret);
> ub960_rxport_write(priv, chan_id, UB960_RR_SLAVE_ALIAS(reg_idx),
> - alias << 1);
> + alias << 1, &ret);
> +
> + if (ret)
> + return ret;
>
> dev_dbg(dev, "rx%u: client 0x%02x assigned alias 0x%02x at slot %u\n",
> - rxport->nport, client->addr, alias, reg_idx);
> + rxport->nport, addr, alias, reg_idx);
>
> return 0;
> }
> @@@ -1089,11 -1306,10 +1311,12 @@@ static void ub960_atr_detach_addr(struc
> struct ub960_rxport *rxport = priv->rxports[chan_id];
> struct device *dev = &priv->client->dev;
> unsigned int reg_idx;
> + int ret;
>
> - for (reg_idx = 0; reg_idx < ARRAY_SIZE(rxport->aliased_clients); reg_idx++) {
> - if (rxport->aliased_clients[reg_idx] == client)
> + guard(mutex)(&rxport->aliased_addrs_lock);
> +
> + for (reg_idx = 0; reg_idx < ARRAY_SIZE(rxport->aliased_addrs); reg_idx++) {
> + if (rxport->aliased_addrs[reg_idx] == addr)
> break;
> }
>
> @@@ -1103,12 -1319,18 +1326,18 @@@
> return;
> }
>
> - rxport->aliased_clients[reg_idx] = NULL;
> + rxport->aliased_addrs[reg_idx] = 0;
>
> - ub960_rxport_write(priv, chan_id, UB960_RR_SLAVE_ALIAS(reg_idx), 0);
> + ret = ub960_rxport_write(priv, chan_id, UB960_RR_SLAVE_ALIAS(reg_idx),
> + 0, NULL);
> + if (ret) {
> + dev_err(dev, "rx%u: unable to fully unmap client 0x%02x: %d\n",
> - rxport->nport, client->addr, ret);
> ++ rxport->nport, addr, ret);
> + return;
> + }
>
> dev_dbg(dev, "rx%u: client 0x%02x released at slot %u\n", rxport->nport,
> - client->addr, reg_idx);
> + addr, reg_idx);
> }
>
> static const struct i2c_atr_ops ub960_atr_ops = {
> @@@ -3231,21 -4370,12 +4376,14 @@@ static void ub960_txport_free_ports(str
>
> static void ub960_rxport_free_ports(struct ub960_data *priv)
> {
> - unsigned int nport;
> + for_each_active_rxport(priv, it) {
> + fwnode_handle_put(it.rxport->source.ep_fwnode);
> + fwnode_handle_put(it.rxport->ser.fwnode);
>
> - for (nport = 0; nport < priv->hw_data->num_rxports; nport++) {
> - struct ub960_rxport *rxport = priv->rxports[nport];
> ++ mutex_destroy(&it.rxport->aliased_addrs_lock);
> +
> - if (!rxport)
> - continue;
> -
> - fwnode_handle_put(rxport->source.ep_fwnode);
> - fwnode_handle_put(rxport->ser.fwnode);
> -
> - mutex_destroy(&rxport->aliased_addrs_lock);
> -
> - kfree(rxport);
> - priv->rxports[nport] = NULL;
> + kfree(it.rxport);
> + priv->rxports[it.nport] = NULL;
> }
> }
This is now a conflict between the i2c tree and Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-05-29 2:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 0:49 linux-next: manual merge of the v4l-dvb tree with the i2c tree Stephen Rothwell
2025-04-28 1:22 ` Stephen Rothwell
2025-04-28 1:30 ` Stephen Rothwell
2025-04-29 11:46 ` Tomi Valkeinen
2025-05-29 2:49 ` Stephen Rothwell [this message]
2025-05-30 8:13 ` Romain Gantois
2025-05-30 11:24 ` Wolfram Sang
2025-06-02 16:17 ` Romain Gantois
2025-05-31 12:05 ` Wolfram Sang
2025-06-02 15:57 ` Romain Gantois
-- strict thread matches above, loose matches on Subject: below --
2013-04-03 1:12 Stephen Rothwell
2013-05-01 3:27 ` Stephen Rothwell
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=20250529124929.5217c6d9@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=hverkuil@xs4all.nl \
--cc=jai.luthra@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=romain.gantois@bootlin.com \
--cc=sakari.ailus@linux.intel.com \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=wsa+renesas@sang-engineering.com \
--cc=wsa@the-dreams.de \
/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