From: Nuno Sa via B4 Relay <devnull+nuno.sa.analog.com@kernel.org> To: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-iio@vger.kernel.org Cc: Olivier MOYSAN <olivier.moysan@foss.st.com>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, "Rafael J. Wysocki" <rafael@kernel.org>, Rob Herring <robh+dt@kernel.org>, Frank Rowand <frowand.list@gmail.com>, Jonathan Cameron <jic23@kernel.org>, Lars-Peter Clausen <lars@metafoo.de>, Michael Hennerich <Michael.Hennerich@analog.com>, Nuno Sa <nuno.sa@analog.com> Subject: [PATCH 01/12] driver: core: allow modifying device_links flags Date: Tue, 21 Nov 2023 11:20:14 +0100 [thread overview] Message-ID: <20231121-dev-iio-backend-v1-1-6a3d542eba35@analog.com> (raw) In-Reply-To: <20231121-dev-iio-backend-v1-0-6a3d542eba35@analog.com> From: Nuno Sa <nuno.sa@analog.com> If a device_link is previously created (eg: via fw_devlink_create_devlink()) before the supplier + consumer are both present and bound to their respective drivers, there's no way to set DL_FLAG_AUTOREMOVE_CONSUMER anymore while one can still set DL_FLAG_AUTOREMOVE_SUPPLIER. Hence, rework the flags checks to allow for DL_FLAG_AUTOREMOVE_CONSUMER in the same way DL_FLAG_AUTOREMOVE_SUPPLIER is done. While at it, make sure that we are never left with DL_FLAG_AUTOPROBE_CONSUMER set together with one of DL_FLAG_AUTOREMOVE_CONSUMER or DL_FLAG_AUTOREMOVE_SUPPLIER. Signed-off-by: Nuno Sa <nuno.sa@analog.com> --- drivers/base/core.c | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/drivers/base/core.c b/drivers/base/core.c index 4d8b315c48a1..b6aac55c361d 100644 --- a/drivers/base/core.c +++ b/drivers/base/core.c @@ -806,11 +806,15 @@ struct device_link *device_link_add(struct device *consumer, * update the existing link to stay around longer. */ if (flags & DL_FLAG_AUTOREMOVE_SUPPLIER) { - if (link->flags & DL_FLAG_AUTOREMOVE_CONSUMER) { - link->flags &= ~DL_FLAG_AUTOREMOVE_CONSUMER; - link->flags |= DL_FLAG_AUTOREMOVE_SUPPLIER; - } - } else if (!(flags & DL_FLAG_AUTOREMOVE_CONSUMER)) { + link->flags &= ~DL_FLAG_AUTOREMOVE_CONSUMER; + link->flags &= ~DL_FLAG_AUTOPROBE_CONSUMER; + link->flags |= DL_FLAG_AUTOREMOVE_SUPPLIER; + + } else if (flags & DL_FLAG_AUTOREMOVE_CONSUMER) { + link->flags &= ~DL_FLAG_AUTOREMOVE_SUPPLIER; + link->flags &= ~DL_FLAG_AUTOPROBE_CONSUMER; + link->flags |= DL_FLAG_AUTOREMOVE_CONSUMER; + } else { link->flags &= ~(DL_FLAG_AUTOREMOVE_CONSUMER | DL_FLAG_AUTOREMOVE_SUPPLIER); } -- 2.42.1
WARNING: multiple messages have this Message-ID (diff)
From: Nuno Sa <nuno.sa@analog.com> To: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-iio@vger.kernel.org Cc: Olivier MOYSAN <olivier.moysan@foss.st.com>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, "Rafael J. Wysocki" <rafael@kernel.org>, Rob Herring <robh+dt@kernel.org>, Frank Rowand <frowand.list@gmail.com>, Jonathan Cameron <jic23@kernel.org>, Lars-Peter Clausen <lars@metafoo.de>, Michael Hennerich <Michael.Hennerich@analog.com>, Nuno Sa <nuno.sa@analog.com> Subject: [PATCH 01/12] driver: core: allow modifying device_links flags Date: Tue, 21 Nov 2023 11:20:14 +0100 [thread overview] Message-ID: <20231121-dev-iio-backend-v1-1-6a3d542eba35@analog.com> (raw) In-Reply-To: <20231121-dev-iio-backend-v1-0-6a3d542eba35@analog.com> If a device_link is previously created (eg: via fw_devlink_create_devlink()) before the supplier + consumer are both present and bound to their respective drivers, there's no way to set DL_FLAG_AUTOREMOVE_CONSUMER anymore while one can still set DL_FLAG_AUTOREMOVE_SUPPLIER. Hence, rework the flags checks to allow for DL_FLAG_AUTOREMOVE_CONSUMER in the same way DL_FLAG_AUTOREMOVE_SUPPLIER is done. While at it, make sure that we are never left with DL_FLAG_AUTOPROBE_CONSUMER set together with one of DL_FLAG_AUTOREMOVE_CONSUMER or DL_FLAG_AUTOREMOVE_SUPPLIER. Signed-off-by: Nuno Sa <nuno.sa@analog.com> --- drivers/base/core.c | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/drivers/base/core.c b/drivers/base/core.c index 4d8b315c48a1..b6aac55c361d 100644 --- a/drivers/base/core.c +++ b/drivers/base/core.c @@ -806,11 +806,15 @@ struct device_link *device_link_add(struct device *consumer, * update the existing link to stay around longer. */ if (flags & DL_FLAG_AUTOREMOVE_SUPPLIER) { - if (link->flags & DL_FLAG_AUTOREMOVE_CONSUMER) { - link->flags &= ~DL_FLAG_AUTOREMOVE_CONSUMER; - link->flags |= DL_FLAG_AUTOREMOVE_SUPPLIER; - } - } else if (!(flags & DL_FLAG_AUTOREMOVE_CONSUMER)) { + link->flags &= ~DL_FLAG_AUTOREMOVE_CONSUMER; + link->flags &= ~DL_FLAG_AUTOPROBE_CONSUMER; + link->flags |= DL_FLAG_AUTOREMOVE_SUPPLIER; + + } else if (flags & DL_FLAG_AUTOREMOVE_CONSUMER) { + link->flags &= ~DL_FLAG_AUTOREMOVE_SUPPLIER; + link->flags &= ~DL_FLAG_AUTOPROBE_CONSUMER; + link->flags |= DL_FLAG_AUTOREMOVE_CONSUMER; + } else { link->flags &= ~(DL_FLAG_AUTOREMOVE_CONSUMER | DL_FLAG_AUTOREMOVE_SUPPLIER); } -- 2.42.1
next prev parent reply other threads:[~2023-11-21 10:17 UTC|newest] Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-21 10:20 [PATCH 00/12] iio: add new backend framework Nuno Sa via B4 Relay 2023-11-21 10:20 ` Nuno Sa 2023-11-21 10:20 ` Nuno Sa via B4 Relay [this message] 2023-11-21 10:20 ` [PATCH 01/12] driver: core: allow modifying device_links flags Nuno Sa 2023-11-21 10:20 ` [PATCH 02/12] of: property: add device link support for io-backends Nuno Sa via B4 Relay 2023-11-21 10:20 ` Nuno Sa 2023-11-21 10:20 ` [PATCH 03/12] iio: add the IIO backend framework Nuno Sa via B4 Relay 2023-11-21 10:20 ` Nuno Sa 2023-12-04 15:38 ` Jonathan Cameron 2023-12-06 12:05 ` Nuno Sá 2023-12-06 17:15 ` Jonathan Cameron 2023-11-21 10:20 ` [PATCH 04/12] iio: adc: ad9467: fix reset gpio handling Nuno Sa via B4 Relay 2023-11-21 10:20 ` Nuno Sa 2023-11-30 21:41 ` David Lechner 2023-12-01 8:47 ` Nuno Sá 2023-12-01 17:01 ` David Lechner 2023-12-02 8:36 ` Nuno Sá 2023-12-04 15:15 ` Jonathan Cameron 2023-12-04 16:41 ` Nuno Sá 2023-11-21 10:20 ` [PATCH 05/12] iio: adc: ad9467: don't ignore error codes Nuno Sa via B4 Relay 2023-11-21 10:20 ` Nuno Sa 2023-11-30 21:44 ` David Lechner 2023-12-01 8:47 ` Nuno Sá 2023-12-04 15:19 ` Jonathan Cameron 2023-11-21 10:20 ` [PATCH 06/12] iio: adc: ad9467: add mutex to struct ad9467_state Nuno Sa via B4 Relay 2023-11-21 10:20 ` Nuno Sa 2023-11-30 21:50 ` David Lechner 2023-12-01 8:49 ` Nuno Sá 2023-12-04 15:21 ` Jonathan Cameron 2023-12-04 15:23 ` Jonathan Cameron 2023-12-04 16:10 ` Nuno Sá 2023-12-04 16:51 ` Jonathan Cameron 2023-11-21 10:20 ` [PATCH 07/12] iio: adc: ad9467: fix scale setting Nuno Sa via B4 Relay 2023-11-21 10:20 ` Nuno Sa 2023-11-21 10:20 ` [PATCH 08/12] iio: adc: ad9467: use spi_get_device_match_data() Nuno Sa via B4 Relay 2023-11-21 10:20 ` Nuno Sa 2023-11-21 10:20 ` [PATCH 09/12] iio: adc: ad9467: use chip_info variables instead of array Nuno Sa via B4 Relay 2023-11-21 10:20 ` Nuno Sa 2023-12-04 15:25 ` Jonathan Cameron 2023-12-04 16:24 ` Nuno Sá 2023-11-21 10:20 ` [PATCH 10/12] iio: adc: ad9467: convert to backend framework Nuno Sa via B4 Relay 2023-11-21 10:20 ` Nuno Sa 2023-11-22 0:54 ` kernel test robot 2023-11-30 23:30 ` David Lechner 2023-12-01 0:12 ` David Lechner 2023-12-01 9:08 ` Nuno Sá 2023-12-01 17:44 ` David Lechner 2023-12-02 8:46 ` Nuno Sá 2023-12-04 8:56 ` Nuno Sá 2023-12-04 15:48 ` Jonathan Cameron 2023-12-04 16:23 ` Nuno Sá 2023-12-04 16:57 ` Jonathan Cameron 2023-12-01 9:17 ` Nuno Sá 2023-11-21 10:20 ` [PATCH 11/12] iio: adc: adi-axi-adc: convert to regmap Nuno Sa via B4 Relay 2023-11-21 10:20 ` Nuno Sa 2023-12-04 15:51 ` Jonathan Cameron 2023-12-04 16:15 ` Nuno Sá 2023-11-21 10:20 ` [PATCH 12/12] iio: adc: adi-axi-adc: move to backend framework Nuno Sa via B4 Relay 2023-11-21 10:20 ` Nuno Sa 2023-11-21 23:27 ` kernel test robot 2023-11-25 7:42 ` kernel test robot 2023-11-30 23:33 ` David Lechner 2023-12-01 8:50 ` Nuno Sá 2023-11-23 17:36 ` [PATCH 00/12] iio: add new " Olivier MOYSAN 2023-11-24 9:15 ` Nuno Sá 2023-11-30 23:54 ` David Lechner 2023-12-01 8:41 ` Nuno Sá 2023-12-01 9:14 ` Nuno Sá 2023-12-02 3:53 ` David Lechner 2023-12-02 9:37 ` Nuno Sá 2023-12-02 16:16 ` David Lechner 2023-12-04 14:49 ` Jonathan Cameron
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=20231121-dev-iio-backend-v1-1-6a3d542eba35@analog.com \ --to=devnull+nuno.sa.analog.com@kernel.org \ --cc=Michael.Hennerich@analog.com \ --cc=devicetree@vger.kernel.org \ --cc=frowand.list@gmail.com \ --cc=gregkh@linuxfoundation.org \ --cc=jic23@kernel.org \ --cc=lars@metafoo.de \ --cc=linux-iio@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=nuno.sa@analog.com \ --cc=olivier.moysan@foss.st.com \ --cc=rafael@kernel.org \ --cc=robh+dt@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: linkBe 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.