public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: Peter Rosin <peda@axentia.se>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH] i2c: mux: reg: Remove class-based device auto-detection support
Date: Tue, 19 Dec 2023 22:44:46 +0100	[thread overview]
Message-ID: <c9e9cd8b-0056-41be-b62c-223e494fb069@gmail.com> (raw)
In-Reply-To: <69f19443-f2ca-4158-9d25-160db55bfb57@gmail.com>

On 08.11.2023 07:38, Heiner Kallweit wrote:
> Legacy class-based device auto-detection shouldn't be used in new code.
> Therefore remove support in i2c-mux-reg as long as we don't have a
> user of this feature yet.
> 
> Link: https://lore.kernel.org/linux-i2c/a22978a4-88e4-46f4-b71c-032b22321599@gmail.com/
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
> ---
>  drivers/i2c/muxes/i2c-mux-reg.c           | 4 +---
>  include/linux/platform_data/i2c-mux-reg.h | 2 --
>  2 files changed, 1 insertion(+), 5 deletions(-)
> 
> diff --git a/drivers/i2c/muxes/i2c-mux-reg.c b/drivers/i2c/muxes/i2c-mux-reg.c
> index 9efc1ed01..8489971ba 100644
> --- a/drivers/i2c/muxes/i2c-mux-reg.c
> +++ b/drivers/i2c/muxes/i2c-mux-reg.c
> @@ -159,7 +159,6 @@ static int i2c_mux_reg_probe(struct platform_device *pdev)
>  	struct regmux *mux;
>  	struct i2c_adapter *parent;
>  	struct resource *res;
> -	unsigned int class;
>  	int i, ret, nr;
>  
>  	mux = devm_kzalloc(&pdev->dev, sizeof(*mux), GFP_KERNEL);
> @@ -213,9 +212,8 @@ static int i2c_mux_reg_probe(struct platform_device *pdev)
>  
>  	for (i = 0; i < mux->data.n_values; i++) {
>  		nr = mux->data.base_nr ? (mux->data.base_nr + i) : 0;
> -		class = mux->data.classes ? mux->data.classes[i] : 0;
>  
> -		ret = i2c_mux_add_adapter(muxc, nr, mux->data.values[i], class);
> +		ret = i2c_mux_add_adapter(muxc, nr, mux->data.values[i], 0);
>  		if (ret)
>  			goto err_del_mux_adapters;
>  	}
> diff --git a/include/linux/platform_data/i2c-mux-reg.h b/include/linux/platform_data/i2c-mux-reg.h
> index 2543c2a1c..e2e895768 100644
> --- a/include/linux/platform_data/i2c-mux-reg.h
> +++ b/include/linux/platform_data/i2c-mux-reg.h
> @@ -17,7 +17,6 @@
>   * @n_values: Number of multiplexer channels
>   * @little_endian: Indicating if the register is in little endian
>   * @write_only: Reading the register is not allowed by hardware
> - * @classes: Optional I2C auto-detection classes
>   * @idle: Value to write to mux when idle
>   * @idle_in_use: indicate if idle value is in use
>   * @reg: Virtual address of the register to switch channel
> @@ -30,7 +29,6 @@ struct i2c_mux_reg_platform_data {
>  	int n_values;
>  	bool little_endian;
>  	bool write_only;
> -	const unsigned int *classes;
>  	u32 idle;
>  	bool idle_in_use;
>  	void __iomem *reg;

Any feedback on this patch? We're at 6.7-rc6 and I if there's any
feedback I'd like to incorporate it before the 6.8 merge window.


  reply	other threads:[~2023-12-19 21:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08  6:38 [PATCH] i2c: mux: reg: Remove class-based device auto-detection support Heiner Kallweit
2023-12-19 21:44 ` Heiner Kallweit [this message]
2023-12-20 20:45 ` Wolfram Sang
2023-12-20 20:58   ` Heiner Kallweit

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=c9e9cd8b-0056-41be-b62c-223e494fb069@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=peda@axentia.se \
    /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