From: miquel.raynal@bootlin.com (Miquel Raynal)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: dts: nes: add Nintendo NES Classic Edition support
Date: Fri, 9 Mar 2018 10:34:53 +0100 [thread overview]
Message-ID: <20180309103453.56e41ba8@xps13> (raw)
In-Reply-To: <20180309091038.6jxuymerx5lgnh3y@flea.lan>
Hi Maxime,
> > > We want to support the default setup, and not require some hackery to
> > > be done. It will thus be some OTG / peripheral mode, most likely with
> > > an ID pin somewhere.
I would really appreciate to let the comment because with this kind of
boards, almost everything is hackery. Think about the SD card support.
Pins are there, but nothing is wired on it. However we still want to
let these pins available for it.
I can drop the mode = "host" property though.
> On Fri, Mar 09, 2018 at 09:58:14AM +0100, Miquel Raynal wrote:
> > > Since you tested on a SuperNES Classic, I think you should also create
> > > a new DT (possibly include it) with a compatible of its own.
> > >
> > > That way, if we ever find some differences, it will be easy to deal
> > > with them.
> >
> > So, what you would prefer is:
> > 1/ Move this entire DTS but the usb_otg node into a
> > "sun8i-r16-nintendo-nes.dtsi"
> > 2/ Include that DTSI from a
> > "sun8i-r16-nintendo-super-nes-classic-edition.dts" that would add the
> > usb_otg node as it is above.
>
> My remark had nothing to do with USB OTG.
OK, sorry.
> You can just create a DT
> called sun8i-r16-nintendo-nes-classic.dts, and then create another one
> call sun8i-r16-nintendo-supernes-classic.dts that would include the
> former, only overriding the compatible.
And being almost empty then?
>
> Maxime
>
--
Miquel Raynal, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-03-09 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 16:43 [PATCH] arm: dts: nes: add Nintendo NES Classic Edition support Miquel Raynal
2018-03-09 8:26 ` Maxime Ripard
2018-03-09 8:58 ` Miquel Raynal
2018-03-09 9:10 ` Maxime Ripard
2018-03-09 9:34 ` Miquel Raynal [this message]
2018-03-09 10:09 ` Maxime Ripard
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=20180309103453.56e41ba8@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.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