On Thu, 31 Jan 2013, Arnd Bergmann wrote: > On Wednesday 30 January 2013, Guennadi Liakhovetski wrote: > > On Wed, 30 Jan 2013, Arnd Bergmann wrote: > > > > > On Wednesday 30 January 2013, Guennadi Liakhovetski wrote: > > > > > This means, that a multi-platform driver like, e.g. SDHCI cannot use the > > > > > gpio "flags" cell and has to fall-back to always use "*-inverted" > > > > > properties. Same holds for any other multi-arch driver, using GPIOs. So, > > > > > we're stuck with this? > > > > > > But the SDHCI driver itself would not interpret the flags anyway, would it? > > > > Currently each driver, including SDHCI, does it on its own, the goal is to > > do this centrally. And yes, in our specific MMC case, if we want to > > support GPIO controllers with 1 cell, no mmc DT node, using GPIOs for WP > > or CD should be using the inversion flag - even where possible. > > > > > From the code, I understand that of_get_named_gpio() would return a gpio > > > line with the polarity already inverted if it's specified that way, > > > > Sorry, don't understand. of_get_named_gpio() just returns a GPIO number, > > not GPIO level. It doesn't even actually request the GPIO for the specific > > user. Or do you mean, that gpio_chip::of_xlate() should request the chip > > to invert the GPIO from now on? > > I'm not saying that it should, I just thought that it did that already, > but I may be wrong with that. Where does the polarity of a gpio > line normally get set? Well, don't think we had a generic way to handle this until now. Each driver handles GPIOs in its own way. The GPIO API only provides functions to reserve GPIOs, specify their direction (out / in) and set or get level respectively. Besides you could set some flags like GPIOF_OPEN_DRAIN etc. After a driver, say, reads low level of a GPIO it has to decide itself whether it's the "on" or the "off" level, for which many drivers often use their own means to specify GPIO's "polarity." > > > and > > > the SDHCI_QUIRK_INVERTED_WRITE_PROTECT flag can be used to invert it > > > independent of it. > > > > Right, not sure about that flag. Isn't it used for SDHCI-native WP? > > It's used in the sdhci_check_ro() function, independent of whether > the bit comes from the GPIO or from the SDHCI_PRESENT_STATE > register. Right, but the MMC core already has a generic MMC_CAP2_RO_ACTIVE_HIGH flag, so, this flag is redundant. Perhaps, the SDHCI OF glue will have to set that flag if the MMC core reports MMC_CAP2_RO_ACTIVE_HIGH. > It gets set based on the presence of the wp-inverted or the > older sdhci,wp-inverted property, which both get interpreted > in the same way. Right, which is already a mess... > > > So you could actually express the same thing by either > > > putting the inversion into the gpio specifier or into the *-inverted > > > properties. > > > > > > If you actually provide both, that would have the same meaning as not > > > inverting. > > > > Hm, that'd be a weird way to configure the pin, perhaps. > > Yes, it's silly and I don't see a reason why you'd do that, but I think > it should still be considered valid. We can do that, sure, but I'm not sure we really have to apply both to end up with a non-inverted pin, or just interpret it as resundant information and invert once. > > > > BTW, just verified in the current "next": all platforms, using cd-inverted > > > > or wp-inverted in the mainline > > > > > > > > arch/arm/boot/dts/ccu9540.dts > > > > arch/arm/boot/dts/ea3250.dts > > > > arch/arm/boot/dts/phy3250.dts > > > > arch/arm/boot/dts/snowball.dts > > > > arch/arm/boot/dts/u9540.dts > > > > > > > > use GPIO controllers with 2 or 3 cells. > > > > > > What about those that don't use a GPIO line at all but instead use a > > > built-in write-protect and card-detect registers of the SDHCI controller? > > > > The mmc.txt document specifies cd-inverted and wp-inverted _explicitly_ > > for use with GPIOs. If we want to use them with built-in CD and WP pins, > > we have to modify those definitions too. > > Yes, that makes sense. The way that the specific esdhc binding is written > does not refer to gpio and could be interpreted the way that it is used > in the driver (for both gpio and internal wp), but it's certainly a > good idea to clarify it in the common binding. Ok, as soon as we agree on handling of the double inversion, I'll prepare and post an updated patch series. Thanks Guennadi --- Guennadi Liakhovetski, Ph.D. Freelance Open-Source Software Developer http://www.open-technology.de/ -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
