devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Maxime Ripard
	<maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
	devicetree <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	linux-sunxi <linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re-using sun5i-a13.dtsi for the r8 ?
Date: Fri, 21 Aug 2015 09:53:07 +0200	[thread overview]
Message-ID: <55D6D8E3.3020403@redhat.com> (raw)

Hi Maxime,

I just realized that I never answered your question about the need
for a tvencoder simplefb node in sun5i-a13.dtsi, like the one from
the "ARM: dts: sun5i: Add simplefb node for tvencoder output"

I think the real question is do we want to use sun5i-a13.dtsi for
the r8 ?

I would expect us to use a sun5i-r8.dtsi, this one could then
include sun5i-a13.dtsi, and have the extra simplefb node for
the tvencoder. Putting the simplefb node for the tvencoder
in sun5i-a13.dtsi feels wrong because the A13 package does
not have a tvout pin.

Does that sound like a good solution to you ?

Regards,

Hans
--
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

             reply	other threads:[~2015-08-21  7:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21  7:53 Hans de Goede [this message]
     [not found] ` <55D6D8E3.3020403-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-08-24 14:26   ` Re-using sun5i-a13.dtsi for the r8 ? Maxime Ripard
2015-08-25  0:24     ` Julian Calaby
     [not found]       ` <CAGRGNgW06-znXSnPKS3nfU_FseTZ0OcMea5qEzHVaTkpRfXHUg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-08-25  5:14         ` Maxime Ripard
2015-08-25  5:27           ` Julian Calaby

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=55D6D8E3.3020403@redhat.com \
    --to=hdegoede-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    --cc=maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@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).