On Fri, Apr 21, 2017 at 08:29:40AM +0200, Wolfram Sang wrote:
> Hi Jan,
>
> > What is missing in the pci-driver for ACPI support? We already use ACPI
> > to detect the sclk setting.
>
> I noticed this in the driver:
>
> 134 static int thunder_i2c_smbus_setup(struct octeon_i2c *i2c,
> 135 struct device_node *node)
> 136 {
> 137 /* TODO: ACPI support */
> 138 if (!acpi_disabled)
> 139 return -EOPNOTSUPP;
> 140
> 141 return thunder_i2c_smbus_setup_of(i2c, node);
> 142 }
>
> And from a glimpse, I assumed this is the place to detect and
> instantiate client devices.
I see. This function is only setting up the optional smbus alert irq
stuff.
> > So, if you're ok with this I'll re-phrase the commit message and
> > re-submit the patch.
>
> I'm OK. It is basically your call. I just wanted to make sure you know
> what it means adding the class to a master driver.
Understood. I think we should look at fully describing the BMC in ACPI
and DT, if that is possible we could get rid of the additional probing.
As we are not there yet I'll post the patch adding the class.
thanks,
Jan
> Regards,
>
> Wolfram
>
--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
