Skip to contentSkip to conversation

i2c: Allow recovery of the initial IRQ by a i2c client device.

PATCH In review Jim Broadus 4 participants 14 messages Feb 16, 2019 – Feb 24, 2019

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 i2c: Allow recovery of the initial IRQ by a i2c client device.

A previous change allowed i2c client devices to discover new IRQs upon reprobe. By clearing the IRQ in i2c_device_remove. However, if an IRQ was assigned in i2c_new_device, that information is lost.

For example, the touchscreen and trackpad devices on a Dell Inspiron laptop are I2C devices whose IRQs are defined by ACPI extended IRQ types. The client device structures are initialized during an ACPI walk. After removing the i2c_hid device, modprobe fails.

This change caches the initial IRQ value in i2c_new_device and then resets the client device IRQ to the initial value in i2c_device_remove.

Fixes 6f108dd70d30 ("i2c: Clear client->irq in i2c_device_remove")
---
 drivers/i2c/i2c-core-base.c | 9 +++++----
 include/linux/i2c.h         | 1 +
 2 files changed, 6 insertions(+), 4 deletions(-)
drivers/i2c/i2c-core-base.c +5 -4
index 28460f6a60cc..af87a16ac3a5 100644
@@ -430,7 +430,7 @@ static int i2c_device_remove(struct device *dev)
 	dev_pm_clear_wake_irq(&client->dev);
 	device_init_wakeup(&client->dev, false);
 
-	client->irq = 0;
+	client->irq = client->init_irq;
 
 	return status;
 }
@@ -741,10 +741,11 @@ i2c_new_device(struct i2c_adapter *adap, struct i2c_board_info const *info)
 	client->flags = info->flags;
 	client->addr = info->addr;
 
-	client->irq = info->irq;
-	if (!client->irq)
-		client->irq = i2c_dev_irq_from_resources(info->resources,
+	client->init_irq = info->irq;
+	if (!client->init_irq)
+		client->init_irq = i2c_dev_irq_from_resources(info->resources,
 							 info->num_resources);
+	client->irq = client->init_irq;
 
 	strlcpy(client->name, info->type, sizeof(client->name));
 
include/linux/i2c.h +1 -0
index 65b4eaed1d96..7e748648c7d3 100644
@@ -333,6 +333,7 @@ struct i2c_client {
 	char name[I2C_NAME_SIZE];
 	struct i2c_adapter *adapter;	/* the adapter we sit on	*/
 	struct device dev;		/* the device structure		*/
+	int init_irq;			/* irq set at initialization	*/
 	int irq;			/* irq issued by device		*/
 	struct list_head detected;
 #if IS_ENABLED(CONFIG_I2C_SLAVE)
Signature · 1 line
2.20.1
Reviewed-by on v1 1/1
#1 lore raw
Quoted 9 lines · Jim Broadus

A previous change allowed i2c client devices to discover new IRQs upon reprobe. By clearing the IRQ in i2c_device_remove. However, if an IRQ was assigned in i2c_new_device, that information is lost.

For example, the touchscreen and trackpad devices on a Dell Inspiron laptop are I2C devices whose IRQs are defined by ACPI extended IRQ types. The client device structures are initialized during an ACPI walk. After removing the i2c_hid device, modprobe fails.

Quoted 6 lines

This change caches the initial IRQ value in i2c_new_device and then resets the client device IRQ to the initial value in i2c_device_remove.

Fixes 6f108dd70d30 ("i2c: Clear client->irq in i2c_device_remove")

---

Apologies for the issues caused. I think this looks like a good fix to me.

Thanks,
Charles

#2 lore raw

Thank you Charles. I should probably correct the typos in my commit message.

Quoted 25 lines · Charles Keepax
Quoted 9 lines · Jim Broadus

A previous change allowed i2c client devices to discover new IRQs upon reprobe. By clearing the IRQ in i2c_device_remove. However, if an IRQ was assigned in i2c_new_device, that information is lost.

For example, the touchscreen and trackpad devices on a Dell Inspiron laptop are I2C devices whose IRQs are defined by ACPI extended IRQ types. The client device structures are initialized during an ACPI walk. After removing the i2c_hid device, modprobe fails.

Quoted 6 lines

This change caches the initial IRQ value in i2c_new_device and then resets the client device IRQ to the initial value in i2c_device_remove.

Fixes 6f108dd70d30 ("i2c: Clear client->irq in i2c_device_remove")

---

Apologies for the issues caused. I think this looks like a good fix to me.

Thanks,
Charles

#3 lore raw

PATCH 1/1 i2c: Allow recovery of the initial IRQ by an I2C client device.

A previous change allowed I2C client devices to discover new IRQs upon reprobe by clearing the IRQ in i2c_device_remove. However, if an IRQ was assigned in i2c_new_device, that information is lost.

For example, the touchscreen and trackpad devices on a Dell Inspiron laptop are I2C devices whose IRQs are defined by ACPI extended IRQ types. The client device structures are initialized during an ACPI walk. After removing the i2c_hid device, modprobe fails.

This change caches the initial IRQ value in i2c_new_device and then resets the client device IRQ to the initial value in i2c_device_remove.

Fixes 6f108dd70d30 ("i2c: Clear client->irq in i2c_device_remove")
---
 drivers/i2c/i2c-core-base.c | 9 +++++----
 include/linux/i2c.h         | 1 +
 2 files changed, 6 insertions(+), 4 deletions(-)
drivers/i2c/i2c-core-base.c +5 -4
index 28460f6a60cc..af87a16ac3a5 100644
@@ -430,7 +430,7 @@ static int i2c_device_remove(struct device *dev)
 	dev_pm_clear_wake_irq(&client->dev);
 	device_init_wakeup(&client->dev, false);
 
-	client->irq = 0;
+	client->irq = client->init_irq;
 
 	return status;
 }
@@ -741,10 +741,11 @@ i2c_new_device(struct i2c_adapter *adap, struct i2c_board_info const *info)
 	client->flags = info->flags;
 	client->addr = info->addr;
 
-	client->irq = info->irq;
-	if (!client->irq)
-		client->irq = i2c_dev_irq_from_resources(info->resources,
+	client->init_irq = info->irq;
+	if (!client->init_irq)
+		client->init_irq = i2c_dev_irq_from_resources(info->resources,
 							 info->num_resources);
+	client->irq = client->init_irq;
 
 	strlcpy(client->name, info->type, sizeof(client->name));
 
include/linux/i2c.h +1 -0
index 65b4eaed1d96..7e748648c7d3 100644
@@ -333,6 +333,7 @@ struct i2c_client {
 	char name[I2C_NAME_SIZE];
 	struct i2c_adapter *adapter;	/* the adapter we sit on	*/
 	struct device dev;		/* the device structure		*/
+	int init_irq;			/* irq set at initialization	*/
 	int irq;			/* irq issued by device		*/
 	struct list_head detected;
 #if IS_ENABLED(CONFIG_I2C_SLAVE)
Signature · 1 line
2.20.1
#4 lore raw

Re: [PATCH] i2c: Allow recovery of the initial IRQ by an I2C client device.

Apologies.. This should have been marked v2.

Quoted 63 lines · Jim Broadus

A previous change allowed I2C client devices to discover new IRQs upon reprobe by clearing the IRQ in i2c_device_remove. However, if an IRQ was assigned in i2c_new_device, that information is lost.

For example, the touchscreen and trackpad devices on a Dell Inspiron laptop are I2C devices whose IRQs are defined by ACPI extended IRQ types. The client device structures are initialized during an ACPI walk. After removing the i2c_hid device, modprobe fails.

This change caches the initial IRQ value in i2c_new_device and then resets the client device IRQ to the initial value in i2c_device_remove.

Fixes 6f108dd70d30 ("i2c: Clear client->irq in i2c_device_remove")
---
 drivers/i2c/i2c-core-base.c | 9 +++++----
 include/linux/i2c.h         | 1 +
 2 files changed, 6 insertions(+), 4 deletions(-)
drivers/i2c/i2c-core-base.c +5 -4
index 28460f6a60cc..af87a16ac3a5 100644
@@ -430,7 +430,7 @@ static int i2c_device_remove(struct device *dev)
        dev_pm_clear_wake_irq(&client->dev);
        device_init_wakeup(&client->dev, false);
 
-       client->irq = 0;
+       client->irq = client->init_irq;
 
        return status;
 }
@@ -741,10 +741,11 @@ i2c_new_device(struct i2c_adapter *adap, struct i2c_board_info const *info)
        client->flags = info->flags;
        client->addr = info->addr;
 
-       client->irq = info->irq;
-       if (!client->irq)
-               client->irq = i2c_dev_irq_from_resources(info->resources,
+       client->init_irq = info->irq;
+       if (!client->init_irq)
+               client->init_irq = i2c_dev_irq_from_resources(info->resources,
                                                         info->num_resources);
+       client->irq = client->init_irq;
 
        strlcpy(client->name, info->type, sizeof(client->name));
 
include/linux/i2c.h +1 -1
index 65b4eaed1d96..7e748648c7d3 100644
@@ -333,6 +333,7 @@ struct i2c_client {
        char name[I2C_NAME_SIZE];
        struct i2c_adapter *adapter;    /* the adapter we sit on        */
        struct device dev;              /* the device structure         */
+       int init_irq;                   /* irq set at initialization    */
        int irq;                        /* irq issued by device         */
        struct list_head detected;
 #if IS_ENABLED(CONFIG_I2C_SLAVE)
--

2.20.1

#5 lore raw

Re: [PATCH] i2c: Allow recovery of the initial IRQ by an I2C client device.

In reply to Jim Broadus
Quoted 9 lines · Jim Broadus

A previous change allowed I2C client devices to discover new IRQs upon reprobe by clearing the IRQ in i2c_device_remove. However, if an IRQ was assigned in i2c_new_device, that information is lost.

For example, the touchscreen and trackpad devices on a Dell Inspiron laptop are I2C devices whose IRQs are defined by ACPI extended IRQ types. The client device structures are initialized during an ACPI walk. After removing the i2c_hid device, modprobe fails.

Quoted 5 lines

This change caches the initial IRQ value in i2c_new_device and then resets the client device IRQ to the initial value in i2c_device_remove.

Fixes 6f108dd70d30 ("i2c: Clear client->irq in i2c_device_remove")

Adding Benjamin to CC

Quoted 48 lines
---
 drivers/i2c/i2c-core-base.c | 9 +++++----
 include/linux/i2c.h         | 1 +
 2 files changed, 6 insertions(+), 4 deletions(-)
drivers/i2c/i2c-core-base.c +5 -4
index 28460f6a60cc..af87a16ac3a5 100644
@@ -430,7 +430,7 @@ static int i2c_device_remove(struct device *dev)
 	dev_pm_clear_wake_irq(&client->dev);
 	device_init_wakeup(&client->dev, false);
 
-	client->irq = 0;
+	client->irq = client->init_irq;
 
 	return status;
 }
@@ -741,10 +741,11 @@ i2c_new_device(struct i2c_adapter *adap, struct i2c_board_info const *info)
 	client->flags = info->flags;
 	client->addr = info->addr;
 
-	client->irq = info->irq;
-	if (!client->irq)
-		client->irq = i2c_dev_irq_from_resources(info->resources,
+	client->init_irq = info->irq;
+	if (!client->init_irq)
+		client->init_irq = i2c_dev_irq_from_resources(info->resources,
 							 info->num_resources);
+	client->irq = client->init_irq;
 
 	strlcpy(client->name, info->type, sizeof(client->name));
 
include/linux/i2c.h +1 -0
index 65b4eaed1d96..7e748648c7d3 100644
@@ -333,6 +333,7 @@ struct i2c_client {
 	char name[I2C_NAME_SIZE];
 	struct i2c_adapter *adapter;	/* the adapter we sit on	*/
 	struct device dev;		/* the device structure		*/
+	int init_irq;			/* irq set at initialization	*/
 	int irq;			/* irq issued by device		*/
 	struct list_head detected;
 #if IS_ENABLED(CONFIG_I2C_SLAVE)
Signature · 1 line
2.20.1
Reviewed-by
#6 lore raw

Re: [PATCH] i2c: Allow recovery of the initial IRQ by an I2C client device.

Quoted 11 lines · Wolfram Sang
Quoted 9 lines · Jim Broadus

A previous change allowed I2C client devices to discover new IRQs upon reprobe by clearing the IRQ in i2c_device_remove. However, if an IRQ was assigned in i2c_new_device, that information is lost.

For example, the touchscreen and trackpad devices on a Dell Inspiron laptop are I2C devices whose IRQs are defined by ACPI extended IRQ types. The client device structures are initialized during an ACPI walk. After removing the i2c_hid device, modprobe fails.

Quoted 7 lines
Quoted 5 lines

This change caches the initial IRQ value in i2c_new_device and then resets the client device IRQ to the initial value in i2c_device_remove.

Fixes 6f108dd70d30 ("i2c: Clear client->irq in i2c_device_remove")

Adding Benjamin to CC

Sorry, I should have answered earlier.

I am a little bit hesitant regarding this patch. The effect is correct, and I indeed realized a few weeks ago that something were wrong as we couldn't rmmod/modprobe i2c-hid.

But I still have the feeling that the problem is not solved at the right place. In i2c_new_device() we are storing parts of the fields of struct i2c_board_info, and when resetting the irq we are losing information. This patch solves that, but I wonder if the IRQ should not be 'simply' set in i2c_device_probe(). This means we also need to store the .resources of info, but I have a feeling this will be less error prone in the future.

But this is just my guts telling me something is not right. I would perfectly understand if we want to get this merged ASAP.

So given that the code is correct, this is my:

But at least I have expressed my feelings :)

Cheers,
Benjamin

Quoted 49 lines
Quoted 49 lines
---
 drivers/i2c/i2c-core-base.c | 9 +++++----
 include/linux/i2c.h         | 1 +
 2 files changed, 6 insertions(+), 4 deletions(-)
drivers/i2c/i2c-core-base.c +5 -4
index 28460f6a60cc..af87a16ac3a5 100644
@@ -430,7 +430,7 @@ static int i2c_device_remove(struct device *dev)
      dev_pm_clear_wake_irq(&client->dev);
      device_init_wakeup(&client->dev, false);
 
-     client->irq = 0;
+     client->irq = client->init_irq;
 
      return status;
 }
@@ -741,10 +741,11 @@ i2c_new_device(struct i2c_adapter *adap, struct i2c_board_info const *info)
      client->flags = info->flags;
      client->addr = info->addr;
 
-     client->irq = info->irq;
-     if (!client->irq)
-             client->irq = i2c_dev_irq_from_resources(info->resources,
+     client->init_irq = info->irq;
+     if (!client->init_irq)
+             client->init_irq = i2c_dev_irq_from_resources(info->resources,
                                                       info->num_resources);
+     client->irq = client->init_irq;
 
      strlcpy(client->name, info->type, sizeof(client->name));
 
include/linux/i2c.h +1 -1
index 65b4eaed1d96..7e748648c7d3 100644
@@ -333,6 +333,7 @@ struct i2c_client {
      char name[I2C_NAME_SIZE];
      struct i2c_adapter *adapter;    /* the adapter we sit on        */
      struct device dev;              /* the device structure         */
+     int init_irq;                   /* irq set at initialization    */
      int irq;                        /* irq issued by device         */
      struct list_head detected;
 #if IS_ENABLED(CONFIG_I2C_SLAVE)
--

2.20.1

#7 lore raw

Re: [PATCH] i2c: Allow recovery of the initial IRQ by an I2C client device.

Quoted 34 lines · Benjamin Tissoires
Quoted 11 lines · Wolfram Sang
Quoted 9 lines · Jim Broadus

A previous change allowed I2C client devices to discover new IRQs upon reprobe by clearing the IRQ in i2c_device_remove. However, if an IRQ was assigned in i2c_new_device, that information is lost.

For example, the touchscreen and trackpad devices on a Dell Inspiron laptop are I2C devices whose IRQs are defined by ACPI extended IRQ types. The client device structures are initialized during an ACPI walk. After removing the i2c_hid device, modprobe fails.

Quoted 7 lines
Quoted 5 lines

This change caches the initial IRQ value in i2c_new_device and then resets the client device IRQ to the initial value in i2c_device_remove.

Fixes 6f108dd70d30 ("i2c: Clear client->irq in i2c_device_remove")

Adding Benjamin to CC

Sorry, I should have answered earlier.

I am a little bit hesitant regarding this patch. The effect is correct, and I indeed realized a few weeks ago that something were wrong as we couldn't rmmod/modprobe i2c-hid.

But I still have the feeling that the problem is not solved at the right place. In i2c_new_device() we are storing parts of the fields of struct i2c_board_info, and when resetting the irq we are losing information. This patch solves that, but I wonder if the IRQ should not be 'simply' set in i2c_device_probe(). This means we also need to store the .resources of info, but I have a feeling this will be less error prone in the future.

Quoted 7 lines

But this is just my guts telling me something is not right. I would perfectly understand if we want to get this merged ASAP.

So given that the code is correct, this is my:

But at least I have expressed my feelings :)

Which I can relate to very much. I see the code solves the issue but my feeling is that we are patching around something which should be handled differently in general.

Is somebody willing to research this further?

Thanks for your input.

#8 lore raw

Re: [PATCH] i2c: Allow recovery of the initial IRQ by an I2C client device.

Quoted 42 lines · Wolfram Sang
Quoted 33 lines · Benjamin Tissoires
Quoted 10 lines · Wolfram Sang
Quoted 9 lines · Jim Broadus

A previous change allowed I2C client devices to discover new IRQs upon reprobe by clearing the IRQ in i2c_device_remove. However, if an IRQ was assigned in i2c_new_device, that information is lost.

For example, the touchscreen and trackpad devices on a Dell Inspiron laptop are I2C devices whose IRQs are defined by ACPI extended IRQ types. The client device structures are initialized during an ACPI walk. After removing the i2c_hid device, modprobe fails.

Quoted 7 lines
Quoted 5 lines

This change caches the initial IRQ value in i2c_new_device and then resets the client device IRQ to the initial value in i2c_device_remove.

Fixes 6f108dd70d30 ("i2c: Clear client->irq in i2c_device_remove")

Adding Benjamin to CC

Sorry, I should have answered earlier.

I am a little bit hesitant regarding this patch. The effect is correct, and I indeed realized a few weeks ago that something were wrong as we couldn't rmmod/modprobe i2c-hid.

But I still have the feeling that the problem is not solved at the right place. In i2c_new_device() we are storing parts of the fields of struct i2c_board_info, and when resetting the irq we are losing information. This patch solves that, but I wonder if the IRQ should not be 'simply' set in i2c_device_probe(). This means we also need to store the .resources of info, but I have a feeling this will be less error prone in the future.

Quoted 7 lines

But this is just my guts telling me something is not right. I would perfectly understand if we want to get this merged ASAP.

So given that the code is correct, this is my:

But at least I have expressed my feelings :)

Quoted 8 lines

Which I can relate to very much. I see the code solves the issue but my feeling is that we are patching around something which should be handled differently in general.

Is somebody willing to research this further?

Thanks for your input.

I would be willing to have more of a look at it but am slightly nervous I am not right person as all the systems I currently work with are DT based so don't really exemplify the issue at all.

Thanks,
Charles

#9 lore raw

Re: [PATCH] i2c: Allow recovery of the initial IRQ by an I2C client device.

Quoted 21 lines
Quoted 21 lines
Quoted 9 lines

But I still have the feeling that the problem is not solved at the right place. In i2c_new_device() we are storing parts of the fields of struct i2c_board_info, and when resetting the irq we are losing information. This patch solves that, but I wonder if the IRQ should not be 'simply' set in i2c_device_probe(). This means we also need to store the .resources of info, but I have a feeling this will be less error prone in the future.

Quoted 7 lines

But this is just my guts telling me something is not right. I would perfectly understand if we want to get this merged ASAP.

So given that the code is correct, this is my:

But at least I have expressed my feelings :)

Which I can relate to very much. I see the code solves the issue but my feeling is that we are patching around something which should be handled differently in general.

Quoted 8 lines
Quoted 4 lines

Is somebody willing to research this further?

Thanks for your input.

I would be willing to have more of a look at it but am slightly nervous I am not right person as all the systems I currently work with are DT based so don't really exemplify the issue at all.

Thank you! Well, I'll be there, too. Discussing, reviewing, testing. And if we have Benjamin for that on board as well, then I think we have a good start for that task :) Others are more than welcome to join, too, of course.

#10 lore raw

Re: [PATCH] i2c: Allow recovery of the initial IRQ by an I2C client device.

Quoted 27 lines · Wolfram Sang
Quoted 27 lines
Quoted 26 lines
Quoted 10 lines

But I still have the feeling that the problem is not solved at the right place. In i2c_new_device() we are storing parts of the fields of struct i2c_board_info, and when resetting the irq we are losing information. This patch solves that, but I wonder if the IRQ should not be 'simply' set in i2c_device_probe(). This means we also need to store the .resources of info, but I have a feeling this will be less error prone in the future.

Quoted 7 lines

But this is just my guts telling me something is not right. I would perfectly understand if we want to get this merged ASAP.

So given that the code is correct, this is my:

But at least I have expressed my feelings :)

Which I can relate to very much. I see the code solves the issue but my feeling is that we are patching around something which should be handled differently in general.

Is somebody willing to research this further?

Thanks for your input.

Quoted 9 lines
Quoted 3 lines

I would be willing to have more of a look at it but am slightly nervous I am not right person as all the systems I currently work with are DT based so don't really exemplify the issue at all.

Thank you! Well, I'll be there, too. Discussing, reviewing, testing. And if we have Benjamin for that on board as well, then I think we have a good start for that task :) Others are more than welcome to join, too, of course.

I'm also more familiar with device-tree (just came across this on my personal laptop) but happy to review and test at the risk of learning something.

#11 lore raw

Re: [PATCH] i2c: Allow recovery of the initial IRQ by an I2C client device.

Quoted 2 lines

I'm also more familiar with device-tree (just came across this on my personal laptop) but happy to review and test at the risk of learning something.

:) Thanks!

#12 lore raw

Re: [PATCH] i2c: Allow recovery of the initial IRQ by an I2C client device.

In reply to Benjamin Tissoires
Quoted 25 lines · Benjamin Tissoires
Quoted 10 lines · Wolfram Sang
Quoted 9 lines · Jim Broadus

A previous change allowed I2C client devices to discover new IRQs upon reprobe by clearing the IRQ in i2c_device_remove. However, if an IRQ was assigned in i2c_new_device, that information is lost.

For example, the touchscreen and trackpad devices on a Dell Inspiron laptop are I2C devices whose IRQs are defined by ACPI extended IRQ types. The client device structures are initialized during an ACPI walk. After removing the i2c_hid device, modprobe fails.

Quoted 7 lines
Quoted 5 lines

This change caches the initial IRQ value in i2c_new_device and then resets the client device IRQ to the initial value in i2c_device_remove.

Fixes 6f108dd70d30 ("i2c: Clear client->irq in i2c_device_remove")

Adding Benjamin to CC

Sorry, I should have answered earlier.

I am a little bit hesitant regarding this patch. The effect is correct, and I indeed realized a few weeks ago that something were wrong as we couldn't rmmod/modprobe i2c-hid.

Quoted 8 lines

But I still have the feeling that the problem is not solved at the right place. In i2c_new_device() we are storing parts of the fields of struct i2c_board_info, and when resetting the irq we are losing information. This patch solves that, but I wonder if the IRQ should not be 'simply' set in i2c_device_probe(). This means we also need to store the .resources of info, but I have a feeling this will be less error prone in the future.

I would be somewhat inclined to agree here, it does seem odd that on some paths we are allocating the IRQ on the new_device side and on some on the probe side.

Quoted 6 lines

But this is just my guts telling me something is not right. I would perfectly understand if we want to get this merged ASAP.

So given that the code is correct, this is my:

This would be my thinking as well we should merge this to avoid the regression.

Thanks,
Charles

Applied
#13 lore raw

Re: [PATCH] i2c: Allow recovery of the initial IRQ by an I2C client device.

In reply to Jim Broadus
Quoted 9 lines · Jim Broadus

A previous change allowed I2C client devices to discover new IRQs upon reprobe by clearing the IRQ in i2c_device_remove. However, if an IRQ was assigned in i2c_new_device, that information is lost.

For example, the touchscreen and trackpad devices on a Dell Inspiron laptop are I2C devices whose IRQs are defined by ACPI extended IRQ types. The client device structures are initialized during an ACPI walk. After removing the i2c_hid device, modprobe fails.

Quoted 5 lines

This change caches the initial IRQ value in i2c_new_device and then resets the client device IRQ to the initial value in i2c_device_remove.

Fixes 6f108dd70d30 ("i2c: Clear client->irq in i2c_device_remove")

Applied to for-next, thanks!

I didn't want to apply to for-current because I didn't feel comfortable changing the I2C core in this very last days before the release.

It will hit linus tree during next merge window and go back to older releases via stable.

That all being said, I'd really love to see the proper fix (move irq assignment from init to probe time) being worked on rather soonish before we forget all the details we know at this moment. I'll be there for it.