> > + iproc_i2c->msg = msg;
> Can it happen that iproc_i2c->msg still holds an uncompleted message
> here or is this serialized by the core? Wolfram? Either here something
We have per-adapter locks serializing transfers, if you mean that?
> > +static int bcm_iproc_i2c_cfg_speed(struct bcm_iproc_i2c_dev *iproc_i2c)
> > +{
> > + unsigned int bus_speed, speed_bit;
> > + u32 val;
> > + int ret = of_property_read_u32(iproc_i2c->device->of_node,
> > + "clock-frequency", &bus_speed);
> > + if (ret < 0) {
> > + dev_err(iproc_i2c->device,
> > + "missing clock-frequency property\n");
> > + return -ENODEV;
> Is a missing property the only situation where of_property_read_u32
> returns an error? Would it be sane to default to 100 kHz?
Default of 100kHz instead of -ENODEV sounds very reasonable.
> > +static int bcm_iproc_i2c_remove(struct platform_device *pdev)
> > +{
> > + struct bcm_iproc_i2c_dev *iproc_i2c = platform_get_drvdata(pdev);
> > +
> > + i2c_del_adapter(&iproc_i2c->adapter);
> You need to free the irq before i2c_del_adapter.
One could also keep using devm_request_irq and disable all interrupts
sources here?
Thanks for the reviews, Uwe!
Wolfram
Attachment:
signature.asc
Description: Digital signature
