Daniel Egger
Daniel Egger
@susu You can create your own dummy GPIO by implementing the required traits as nops.
If you're using hardware magic then you'll have to stick to the rules imposed by it, the driver should not have to care about such implementation specific details. The only...
Plenty of MCUs also have the option of doing some protocol specific handling (even for simple protocols) in hardware but it's very often the best to just disable it and...
Unfortunately I2C doesn't offer a timeout feature so if your connection goes away (or is unstable) there's no standardised way to detect that. SMBUS (an extension of I2C) does specify...
I'm not sure that's what the @dbrgn was requesting, at least I'm reading it differently. > i2c_device.write([0xAB, 0xCD]).unwrap(); This will not work. If the MCU writes to the bus and...
> Check out the AT24CM01. The relevant portion is shown below: Okay, but that is IMHO a different situation and essentially an optimisation to avoid having to handle unprocessed reads/writes...
Yes, please check out #229 for a general proposal to move the Error types from the implementations into embedded-hal for broader and more generic use.
I fully agree there's plenty of room for improvement. We do need to be a bit careful about how we design something generic so it can actually be used by...
That would indeed be ergonomic. But will it actually blend? 😅
Looks excellent. One thing that could be useful is a bridge to `core::time`, which is only `Duration` at the moment.