On Mon, Nov 3, 2014 at 10:09 PM, Doug Anderson <dianders@xxxxxxxxxxxx> wrote:
> On Fri, Oct 31, 2014 at 1:49 AM, Linus Walleij <linus.walleij@xxxxxxxxxx> wrote:
>> Figure out the exact electronic meaning of what happens when you do
>> "output disable" in your hardware, I think it is very likely that
>> PIN_CONFIG_BIAS_HIGH_IMPEDANCE is what you are really
>> after here.
>
> OK, that seems plausible. ...so it is OK to set both
> "bias-high-impedance" _and_ "bias-pull-up" on a pin? That seemed
> weird to me but if that's right I can do that and try to implement
> "bias-high-impedance" on Rockchip...
I don't quite get the question. What this patch does is add something
called "output disable" which I think is analogous to high impedance.
If you enable both as the same time something is likely wrong
because it doesn't make electronic sense, high impedance and
pull up are kind of mutually exclusive. High impedance is also
know as "tristate" and means the line will assume the level of
whatever it is connected to, not try to pull things up.
So either:
- This is the wrong terminology, "output disable" means something
else. Like "disconnect the driver stages" or something, so pull-up
can be enabled.
- Stuff has been programmed in a bad way all the time.
Understanding the hardware is paramount...
> Maybe better to explain the problem. I have a pin that I wish to
> drive high weakly (using a pullup rather than actually pushing
> output-high to the pin). The firmware has left the pin configured as
> an output with no pull.
>
> I can configure the pin like this:
> rockchip,pins = <7 12 RK_FUNC_GPIO &pcfg_pull_up>;
>
> pcfg_pull_up: pcfg-pull-up {
> bias-pull-up;
> };
This makes perfect sense.
> When I do this the current Rockchip pinctrl driver will _not_
> configure me as an input. It will happily flip the "pullup" bit in
> hardware and leave the pin configured as an output.
You seem to imply that the pins registers work such that
input needs to be enabled for pull-up to work.
This is a hardware pecularity. Just enable input in the hardware
whenever pull-up is requested then, as that is how that hardware
has to work. If you want to be explicit there is always
PIN_CONFIG_INPUT_ENABLE (input-enable;)
> I could certainly reach into the GPIO controller part of things
> whenever I see "bias-pull-up" and configure the pin as an input.
I think you should. This is a side effect of combined hardware
and expected.
> I
> guess that wouldn't actually hurt to do even if the pin wasn't
> configured as a GPIO...
This is why we have the callbacks:
pinctrl_request_gpio()
pinctrl_free_gpio()
pinctrl_gpio_direction_input()
pinctrl_gpio_direction_output()
By letting the GPIO driver side call these to set direction, we
can leave the control over direction status and incommensurable
states to the pin control driver.
Not that I have all things in my head, but if you're not using
the above calls in your GPIO driver, I suggest doing so and leaving
the pin direction status for the pinctrl side to handle.
> A third option that would work in my case (and actually be sorta
> clean) would be to implement a faux open-drain output. The hardware
> itself doesn't have a concept of open drain (unlike some SoCs) but I
> could implement it by swapping between "input pulled up" and "output
> driven low".
Uhm. Not following this. Probably you are better at electronics than
I am.
Anyway, I think the answers above is what you actually need to
keep working on this.
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
