On 08/03/2015 09:50 AM, Robert Abel wrote: > Hi Michal, > > On Mon, Aug 3, 2015 at 7:34 AM, Michal Simek <michal.simek@xxxxxxxxxx> wrote: >> Datasheet? version. >> >> Make it DT configurable. > > I'm not sure what you're asking here. This errata isn't covered by any > datasheets and I don't have the time to confirm whether it actually > exists. > I'm thinking it might have been an issue with the old ISR and not the > IP itself (it works fine in simulation when I cause a TX error, then > transmit only SLA afterwards). > I cannot test exhaustively on hardware right now, as I'm not able to > monitor the bus directly on my development platform. Every patch like this has to fix something. If some certain IP versions are affected then it should be listed at least one version. > Because of the above 'hunch', I didn't make this DT configurable, > because I feel either the bug is present and thus the code should > always be run, or the bug doesn't exist. > I don't think it depends on the hardware device, so hence no DT binding. Huh. Don't get what you are saying here. Based on your description it is HW bug and it is completely fine to have dt property to avoid this bug. Having another config property is just not acceptable solution now. Thanks, Michal -- 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
