On Mon, May 09, 2016 at 08:48:59AM +0000, Yao Yuan wrote: > Hi Mark Brown, Please don't top post, reply in line with needed context. This allows readers to readily follow the flow of conversation and understand what you are talking about and also helps ensure that everything in the discussion is being addressed. 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. > There are two problems we have found for use regmap up to now. > 1, Regmap will read device value depends on endian in .dtsi(DSPI in .dtsi file is big-endian) and readl()(readl() in arm64 is le32_to_cpu read) in system. > That is the value read out is fixed regardless the kernel were compiled with CONFIG_CPU_BIG_ENDIAN yes or no. That makes the value(read from DSPI)can't be recognized in one endian mode(CONFIG_CPU_BIG_ENDIAN be set or not). > The result is: DSPI can't working with CONFIG_CPU_BIG_ENDIAN set. This doesn't make sense. If the endianness of the device is specified in DT then the endianness of the CPU won't make a difference. > 2, Sometimes regmap will generate some issues. Some regmap issues will cause the DSPI do not working. > At 2016.4 we find the DSPI was not work, then we found that the regmap R/W the controller register sometimes not right. > The result is: DSPI can't working with REGMAP API. > Although the regmap issues was fast fixed by some giving person. But I'm still tend to use the reliable way. > Regmap is nice and Maybe I should try to fix regmap instead of replacing regmap in my driver. > But regmap is really very large and complex for DSPI driver. Yes, if you find bugs in generic frameworks you should fix them rather than just open coding something.
Attachment:
signature.asc
Description: PGP signature
