devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Rowand <frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Ryan <ryanphilips19-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: dts doubts
Date: Wed, 3 Aug 2016 13:10:48 -0700	[thread overview]
Message-ID: <57A24FC8.7020602@gmail.com> (raw)
In-Reply-To: <CANMsd01Od5J2EX7w-YFXmE+cmpyfq+vs88WeKiO8K0-t=FTmTQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 07/28/16 10:57, Ryan wrote:
> Hello,
> 
> I have certain doubts on dts files. If anyone help me clarify it would
> be helpful.
> 
> 
> Suppose, the following dts file entry is already done in the
> base/parent/included dts file:
> 
> fimc_is_spi_pin1: fimc-is-spi-pin1 {
> samsung,pins = "gpf1-7", "gpf1-6", "gpf1-5", "gpf1-4";
> samsung,pin-function = <2>;
> samsung,pin-pud = <0>;
> samsung,pin-drv = <0>;
> };
> 
> Can i modify the parameters in the child dts file. Say i want to

Yes, you can.  This is a common pattern, for example where a .dtsi file sets

   status = "disabled";

then the including .dts file later changes status to "okay" or "ok".

> modify "samsung,pin-function" or add new parameters to the above
> declaration.
> 
> Thanks for your help.
> --
> To unsubscribe from this list: send the line "unsubscribe devicetree" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2016-08-03 20:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-28 17:57 dts doubts Ryan
     [not found] ` <CANMsd01Od5J2EX7w-YFXmE+cmpyfq+vs88WeKiO8K0-t=FTmTQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-08-03 20:10   ` Frank Rowand [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=57A24FC8.7020602@gmail.com \
    --to=frowand.list-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ryanphilips19-gM/Ye1E23mwN+BqQ9rBEUg@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;
as well as URLs for NNTP newsgroup(s).