Hi Tim.
CB:34385 does not break anything for me because we just use STANDARD speed in our system. It just came to my attention once I had a deeper look at the driver and its evolvement. I just wanted to mention that there are cases where the calculated and reported timing can be suitable for a given speed in coreboot and a speed switch to HIGH in OS (which can be done since the controller supports it and a very similar driver is used at OS-side) will lead to a different timing, worse case not matching the hardware circumstances and therefore ending up in violating the I2C spec.
Werner