Am Donnerstag, den 17.01.2013, 13:55 -0700 schrieb Stephen Warren:
> On 01/17/2013 04:59 AM, Lucas Stach wrote:
> > This adds the device tree include file for the Toradex Colibri T20
> > Computer on Module (COM). It's only valid for the 512MB RAM version of
> > the module, as the 256MB version needs different EMC tables and flash
> > configuration. To make this clear the suffix -512 was added to the board
> > compatible string.
> >
> > The Colibri T20 uses a Tegra2 SoC and has onboard USB Ethernet and AC97
> > sound.
> >
> > Still some things like onboard NAND support missing, but should be a
> > good base for further development.
>
> > diff --git a/arch/arm/boot/dts/tegra20-colibri-512.dtsi b/arch/arm/boot/dts/tegra20-colibri-512.dtsi
>
> > + temperature-sensor@4c {
> > + compatible = "national,lm95245";
>
> You should probably add that compatible value to
> Documentation/devicetree/bindings/i2c/trivial-devices.txt.
>
Yep, will send a separate patch for this.
> > + i2c@7000c000 {
> > + clock-frequency = <400000>;
> > + };
> > +
> > + i2c_ddc: i2c@7000c400 {
> > + clock-frequency = <100000>;
> > + };
> > +
> > + i2c@7000c500 {
> > + clock-frequency = <400000>;
> > + };
>
> > + serial@70006000 {
> > + clock-frequency = <216000000>;
> > + };
> > +
> > + serial@70006300 {
> > + clock-frequency = <216000000>;
> > + };
> > +
> > + usb@c5000000 {
> > + dr_mode = "otg";
> > + };
> > +
> > + usb@c5004000 {
> > + status = "okay";
> > + nvidia,phy-reset-gpio = <&gpio 169 0>; /* gpio PV1 */
> > + };
> > +
> > + sdhci@c8000600 {
> > + cd-gpios = <&gpio 23 0>; /* gpio PC7 */
> > + vmmc-supply = <&ldo5_reg>;
> > + vqmmc-supply = <&vcc_sd_reg>;
> > + };
>
> I assume that all of those nodes are meant to have status="okay"?
>
> Oh, I see those are in the top-level board .dts file. You may as well
> put all the properties there; stuff like the GPIOs and regulators at
> least would be purely specific to the individual board, and not the COM.
>
I would like to keep everything that is defined by the COM to reside in
the COM dtsi. You are right that the regulator in this case is board
specific and should be moved to the board file, I missed this while
splitting things out. But at least the GPIO is defined by the fixed COM
pinout.
> I guess we should really move the serial node's clock-frequency property
> in the SoC .dtsi files.
>
Might be a nice cleanup.
> > + com_regulators {
>
> I think just call that "regulators"; the final board .dts file can
> easily add more sub-nodes to this node, so there's no need to try and
> avoid any naming conflict here. See Cardhu as an example.
>
I don't really see the benefit of merging those nodes. They are separate
regulators, some are located on the COM, others on the carrier board. So
I would like to keep them in separate nodes, unless you have strong
feelings to change this.
--
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
