From: Maxime Ripard <maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
To: Hans de Goede <hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: devicetree <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-sunxi <linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Re-using sun5i-a13.dtsi for the r8 ?
Date: Mon, 24 Aug 2015 16:26:30 +0200 [thread overview]
Message-ID: <20150824142630.GU2413@lukather> (raw)
In-Reply-To: <55D6D8E3.3020403-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 959 bytes --]
Hi,
On Fri, Aug 21, 2015 at 09:53:07AM +0200, Hans de Goede wrote:
> 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 ?
So far, the only information I got about the R8 was that it was
strictly identical to the A13, and it was making sense to re-use it
entirely.
> 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.
But if it turns out it's not, then yeah, we'll have to make another
DTSI.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-08-24 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 7:53 Re-using sun5i-a13.dtsi for the r8 ? Hans de Goede
[not found] ` <55D6D8E3.3020403-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-08-24 14:26 ` Maxime Ripard [this message]
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=20150824142630.GU2413@lukather \
--to=maxime.ripard-wi1+55scjutkeb57/3fjtnbpr1lh4cv8@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@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).