From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [Ac100] [PATCH 3/3] ARM: tegra: paz00: enable nveckeyboard support
Date: Sat, 20 Jul 2013 21:20:52 -0600 [thread overview]
Message-ID: <51EB5394.3090401@wwwdotorg.org> (raw)
In-Reply-To: <3638195.7GdG5goTgS@ax5200p>
On 07/20/2013 03:12 AM, Marc Dietrich wrote:
> On Friday 19 July 2013 13:14:13 Stephen Warren wrote:
...
> Let's skip how this may actually look like in software. Given the discussions
> we had in the past, I propose the following binding:
>
> i2c-slave at 7000c500 {
> compatible = "nvidia,tegra20-i2c-slave";
> reg = <0x7000c500 0x100>;
> interrupts = <0 92 0x04>;
> #address-cells = <1>;
> #size-cells = <0>;
> clock-frequency = <80000>;
> slave-addr = <138>;
Hex would be more common, but that's a minor issue.
> clocks = <&tegra_car 67>, <&tegra_car 124>;
> clock-names = "div-clk", "fast-clk";
>
> nvec {
Above, it says #address-cells=<1>, which means this node needs a reg
property. Perhaps slave-addr should be part of the child nodes (and the
Tegra I2C controller binding would limit itself to supporting only a
single node), so that the same binding style could be applicable to I2C
slave devices that support multiple slave addresses.
> compatible = "nvidia,nvec", "simple-bus";
> protocol = "smbus-request-gpio";
What is that property for; doesn't compatible="nvidia,nvec" already
imply this, or does the NVEC spec define multiple different protocols?
> request-gpios = <&gpio 170 0>; /* gpio PV2 */
We should use the C pre-processor to provide named constants there,
although I guess U-Boot isn't set up for that yet. The kernel is once
this is ported there, and once the 2013.07 release is out, U-Boot should
be able to support this very soon too.
> keyboard {
Simple-bus might require a reg property; I forget. Does the NVEC
protocol include any form of "virtual device address" that it would make
sense to put into a reg property?
> compatible = "nvidia,nvec-keyboard";
> };
> };
> };
>
> Does this looks better?
Yes, overall much better.
New DT bindings should be sent to devicetree at vger.kernel.org for review.
Note that's a branch new list (it moved from a different server), so it
might be best to wait a few days for people to subscribe before sending
mail to it.
next prev parent reply other threads:[~2013-07-21 3:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 8:47 [U-Boot] [PATCH 0/3] ARM: tegra: add nvec keyboard support for paz00 Andrey Danin
2013-07-19 8:47 ` [U-Boot] [PATCH 1/3] ARM: tegra: add nvec driver Andrey Danin
2013-07-19 16:28 ` Tom Warren
2013-07-19 8:47 ` [U-Boot] [PATCH 2/3] ARM: tegra: add input driver for nvec keyboard Andrey Danin
2013-07-19 8:47 ` [U-Boot] [PATCH 3/3] ARM: tegra: paz00: enable nvec keyboard support Andrey Danin
2013-07-19 19:14 ` [U-Boot] [Ac100] " Stephen Warren
2013-07-20 9:12 ` [U-Boot] [Ac100] [PATCH 3/3] ARM: tegra: paz00: enable nveckeyboard support Marc Dietrich
2013-07-21 3:20 ` Stephen Warren [this message]
2013-07-22 8:09 ` [U-Boot] [Ac100] [PATCH 3/3] ARM: tegra: paz00: enable nveckeyboardsupport Marc Dietrich
2013-07-23 15:40 ` Stephen Warren
2013-07-24 17:52 ` Marc Dietrich
2013-07-25 17:40 ` Stephen Warren
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=51EB5394.3090401@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.de \
/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.