On Mon, 2016-10-24 at 00:20 +0200, Linus Walleij wrote: > On Thu, Sep 29, 2016 at 8:45 AM, Joel Stanley <joel@xxxxxxxxx> wrote: > > > > On Wed, Sep 28, 2016 at 12:20 AM, Andrew Jeffery <andrew@xxxxxxxx> wrote: > > > > > > > > On the AST2400 and AST2500 a number of pins depend on state in one of > > > the SIO, LPC or GFX IP blocks, so add support to at least capture what > > > that state is. The pinctrl engine for the Aspeed SoCs doesn't try to > > > inspect or modify the state of the off-SCU IP blocks. Instead, it logs > > > the state requirement with the expectation that the platform > > > designer/maintainer arranges for the appropriate configuration to be > > > applied through the associated drivers. > (...) > > > > > > This is unfortunate. > > > > This patch kicks the can down the road, but doesn't solve the problem > > for a user who wants to configure some functionality that depends on > > the non-SCU bits. Because of this I'm not sure if we want to put it in > > the tree. > > > > However, I'm not sure what a proper solution would look like. Perhaps > > Linus can point out another SoC that has a similar problem? > If I could only understand it. > > Don't you actually want to go and read a few registers on another > IO range? Yes. I guess the hesitation was whether we should also write those registers so we can apply the requested function. > > What we generally do when pin control is spread out in a system is try > to consolidate it, meaning expose the necessary registers on the remote > end using syscon (drivers/mfd/syscon) so that we can easily get a handle > on these registers withe regmap MMIO. > > Since regmap handles atomic access to the registers, that way we > protect from disasters and keep the state in the hardware. This seems like the reasonable approach if we want to read/write those registers. The affected IO ranges correspond to: * SuperIO Controller (SIO) * SOC Display Controller (GFX) * LPC Controller (LPC) SIO and LPC both perform a mishmash of functions and so likely would use the mfd subsystem anyway. I don't yet have any arguments against doing it for the GFX IO space. Joel? > > I don't know if this is helpful. For a normal peripheral you may not want > to put a regmap over all its registers but you prefer to ioremap it, and then > we get the spaghetti of accessor functions to peek and poke into another > peripherals I/O space, and that is undesireable. I briefly experimented with the idea of accessing the other IO spaces but it felt dirty precisely for what would have become accessor spaghetti. So I wound up with the lame approach in this patch, which just punts on the problem. I think the mfd/syscon approach would work well though. It looks like the rockchip pinctrl bindings are doing something along the lines of what we need with the rockchip,pmu phandle property. Is it acceptable to create three properties, a phandle to grab each regmap for the IO spaces above? > > Maybe this is completely not understanding what you want to do, so > sorry, please elaborate. No, seems you have understood what we need to do. > I am afraid the two of you are the only people on > the planet who actually understand what is going on here. > > Also the hardware engineer who wrote the Aspeed pin controller, I would > like to read this persons design specification, I am pretty sure it is very > interesting. Well, presumably this engineer knows too :) And yes, I'd like to know what constraints existed that forced this design as a solution. I'd like my sanity back. > > > > > > > > > - * @reg: The register offset from base in bytes > > > + * @reg: Split into three fields: > > > + * 31:24: IP selector > > > + * 23:12: Reserved > > > + * 11:0: Register offset > That seems like unnecessary shoehorning. Is it reflecting the register layout > of the hardware or are you trying to save bits? For the latter, let it > go and instead > have one member for offset and one member for selector. It doesn't represent the register layout. But saving bits also wasn't the motivation, more avoiding a lot of code churn in the g4/g5 drivers to populate a new member. Maybe that's a bad motivation. I'll have more of a think about it. Thanks for the feedback, Andrew
Attachment:
signature.asc
Description: This is a digitally signed message part
