On Thu, Sep 30, 2021 at 03:06:52PM +0200, Dafna Hirschfeld wrote: > On 30.09.21 14:46, Mark Brown wrote: > > On Thu, Sep 30, 2021 at 02:36:01PM +0200, Dafna Hirschfeld wrote: > > > Actually the original commit not only change that callback 'set_cs_timing' but it also > > > calls 'mtk_spi_set_hw_cs_timing' directly from the function "mtk_spi_prepare_message". > > > So this actually influences all devices bound to this driver (in upstream) > > > I did some printing and it does change values that are written to registers. > > OK, so that's something that should have been in the commit log, > > preferrably in a more detailed form that identifies what the change is. > > However changing the values written out is clearly not the intent of the > > patch and it is a substantially better API so can we not just fix things > > so that the old values are written out? Why are we jumping straight to > > a revert here? > It could be that the values written to the register in the new version of "mtk_spi_set_hw_cs_timing" are the same > as with the previous version. I didn't check that. The difference is that before that patch > the function was not called so it was a dead code. Now it is called and causes erros. > Without the datasheet it is hard to know how to fix it. I responded to that patch two days ago explaining > that but Mason Zhang didn't respond yet. The hardware supports register readback (it's doing a read/modify/write to set the new values) so it should be possible to look at what the default values that get written out are and work out what the default parameters should be set to to give the same effect (instead of 1 which is what's currently used). I would say just skip the delays if they are zero but that means that if only one device on a bus has a delay configured there'd be problems. Please fix your mail client to word wrap within paragraphs at something substantially less than 80 columns. Doing this makes your messages much easier to read and reply to.
Attachment:
signature.asc
Description: PGP signature
