On Mon, Apr 1, 2019 at 11:59 PM H. Nikolaus Schaller <hns@xxxxxxxxxxxxx> wrote: > I learned just some minutes ago that a new patch for gpiolib > came through 5.1-rc3 which does fix this in almost the same way > as I proposed. I am sorry for not being very attentive, I have been travelling. I collected the most urgent fixes and this was fixed as part of that quick patchup. > Except that it seems to check for "cs-gpios" and then disable the > legacy handling. Yups. > So we do not need to add a config option for this legacy > handling (although I'd prefer to have it anyways to remove > some dead code). > > Summary: this series can now be ignored. OK please verify that we are doing things right now, the big worry I have is some interrim DTBs that use the GPIO flag GPIO_ACTIVE_HIGH, which is zero and therefore often the default, and expect it to actually work, while the SPI bindings by definition will ignore that and make the line active low. I'm not very happy about this but it is a result of how we quickly implemented some bindings in the past while the GPIO flags were not yet standardized. Yours, Linus Walleij
