Devicetree
 help / color / mirror / Atom feed
From: Benoit Parrot <bparrot-l0cyMroinI0@public.gmane.org>
To: "Jan Lübbe" <jlu-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: [PATCH RESEND 1/1] ARM: dts: AM33XX: Add LCDC info into am335x-evm
Date: Wed, 26 Jun 2013 17:13:26 -0500	[thread overview]
Message-ID: <20130626221326.GA11798@uda0270506> (raw)
In-Reply-To: <1372143043.4488.50.camel-oeorZI7ca7Kzss5je/eYgj6d/iTt6vPThC4ANOJQIlc@public.gmane.org>

On Tue, Jun 25, 2013 at 08:50:43AM +0200, Jan Lübbe wrote:
> On Mon, 2013-06-24 at 15:32 -0500, Benoit Parrot wrote:
> > Add LCDC device node in DT for am33xx
> > Add LCDC and Panel info in DT for am335x-evm
> 
> > diff --git a/arch/arm/boot/dts/am335x-evm.dts b/arch/arm/boot/dts/am335x-evm.dts
> > index 0423298..40d7a3f 100644
> > --- a/arch/arm/boot/dts/am335x-evm.dts
> > +++ b/arch/arm/boot/dts/am335x-evm.dts
> > @@ -102,6 +136,16 @@
> >  				reg = <0x48>;
> >  			};
> >  		};
> > +
> > +		lcdc {
> > +			compatible = "ti,am33xx-tilcdc";
> > +			reg = <0x4830e000 0x1000>;
> > +			interrupt-parent = <&intc>;
> > +			interrupts = <36>;
> > +			ti,hwmods = "lcdc";
> > +			ti,allow-non-reduced-blanking-modes;
> > +			status = "okay";
> > +		};
> >  	};
> >  
> >  	vbat: fixedregulator@0 {
> >  /include/ "tps65910.dtsi"
> > diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
> > index 8e1248f..05b2c4a 100644
> > --- a/arch/arm/boot/dts/am33xx.dtsi
> > +++ b/arch/arm/boot/dts/am33xx.dtsi
> > @@ -415,5 +415,14 @@
> >  			#size-cells = <1>;
> >  			status = "disabled";
> >  		};
> > +
> > +		lcdc: lcdc@4830e000 {
> > +			compatible = "ti,am33xx-tilcdc";
> > +			reg = <0x4830e000 0x1000>;
> > +			interrupt-parent = <&intc>;
> > +			interrupts = <36>;
> > +			ti,hwmods = "lcdc";
> > +			status = "disabled";
> > +		};
> >  	};
> >  };
> 
> am335x-evm.dts includes am33xx.dtsi, so you shouldn't need to provide
> all SoC-specific settings again in the board dts. The way it's done
> here, you get two nodes ("lcdc" and "lcdc@4830e000") for the same HW
> module.
> 
> It seems you just need status and maybe
> ti,allow-non-reduced-blanking-modes (for which I didn't see either the
> binding or the driver code yet).
> 

Thanks for the feedback. I did miss these cut-paste induced mistake.
I'll update the patch and resubmit.

> Regards,
> Jan
> -- 
> Pengutronix e.K.                           |                             |
> Industrial Linux Solutions                 | http://www.pengutronix.de/  |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
> 

      parent reply	other threads:[~2013-06-26 22:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24 20:32 [PATCH RESEND 1/1] ARM: dts: AM33XX: Add LCDC info into am335x-evm Benoit Parrot
     [not found] ` <1372105967-26669-1-git-send-email-bparrot-l0cyMroinI0@public.gmane.org>
2013-06-25  6:50   ` Jan Lübbe
     [not found]     ` <1372143043.4488.50.camel-oeorZI7ca7Kzss5je/eYgj6d/iTt6vPThC4ANOJQIlc@public.gmane.org>
2013-06-26 22:13       ` Benoit Parrot [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=20130626221326.GA11798@uda0270506 \
    --to=bparrot-l0cymroini0@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=jlu-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox