All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Drew Fustini <drew@beagleboard.org>
Cc: Haojian Zhuang <haojian.zhuang@linaro.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-omap@vger.kernel.org,
	Jason Kridner <jkridner@beagleboard.org>,
	Robert Nelson <robertcnelson@gmail.com>
Subject: Re: [RFC PATCH] pinctrl-single: parse #pinctrl-cells = 2
Date: Wed, 17 Jun 2020 09:54:12 -0700	[thread overview]
Message-ID: <20200617165412.GG37466@atomide.com> (raw)
In-Reply-To: <20200616165314.GC4007093@x1>

* Drew Fustini <drew@beagleboard.org> [200616 16:54]:
> By register masks, do you mean the #define's like PIN_OUTPUT_PULLDOWN
> and MUX_MODE6?
> 
> AM33XX_PADCONF(AM335X_PIN_GPMC_A2, PIN_OUTPUT_PULLDOWN, MUX_MODE6)
> 
> There is a possibility to also use the pinconf properties defined in
> pinctrl-single.c:
> 
> 	static const struct pcs_conf_type prop2[] = {
> 		{ "pinctrl-single,drive-strength", PIN_CONFIG_DRIVE_STRENGTH, },
> 		{ "pinctrl-single,slew-rate", PIN_CONFIG_SLEW_RATE, },
> 		{ "pinctrl-single,input-schmitt", PIN_CONFIG_INPUT_SCHMITT, },
> 		{ "pinctrl-single,low-power-mode", PIN_CONFIG_LOW_POWER_MODE, },
> 	};
> 	static const struct pcs_conf_type prop4[] = {
> 		{ "pinctrl-single,bias-pullup", PIN_CONFIG_BIAS_PULL_UP, },
> 		{ "pinctrl-single,bias-pulldown", PIN_CONFIG_BIAS_PULL_DOWN, },
> 		{ "pinctrl-single,input-schmitt-enable",
> 			PIN_CONFIG_INPUT_SCHMITT_ENABLE, },
> 	};

Oh right I forgot about that :)

> I did some testing with pr_info's sprinkled in and I think those values
> are correct but I would be happy to hear from someone with more insight
> in the design of bias-pulldown and bias-pullup.

OK thanks for testing with the pinconf properties.

Regards,

Tony

      reply	other threads:[~2020-06-17 16:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15 23:09 [RFC PATCH] pinctrl-single: parse #pinctrl-cells = 2 Drew Fustini
2020-06-16 14:26 ` Tony Lindgren
2020-06-16 16:53   ` Drew Fustini
2020-06-17 16:54     ` Tony Lindgren [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200617165412.GG37466@atomide.com \
    --to=tony@atomide.com \
    --cc=drew@beagleboard.org \
    --cc=haojian.zhuang@linaro.org \
    --cc=jkridner@beagleboard.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=robertcnelson@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.