Yes, seems the better solution with less disruption would be trying to do something on patch_realtek.c to deal with this case. Since it's auto config code, must be something that also don't have potential to cause issues on other machines, a specific quirk just for this could be a solution.
@David, thanks for pointing that out.
Yes, seems the better solution with less disruption would be trying to do something on patch_realtek.c to deal with this case. Since it's auto config code, must be something that also don't have potential to cause issues on other machines, a specific quirk just for this could be a solution.