From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 2/2] ARM: dts: imx6q: add Novena board
Date: Tue, 24 Nov 2015 12:04:55 +0100 [thread overview]
Message-ID: <201511241204.55621.marex@denx.de> (raw)
In-Reply-To: <1448270124.3689.2.camel@pengutronix.de>
On Monday, November 23, 2015 at 10:15:24 AM, Lucas Stach wrote:
> Am Freitag, den 20.11.2015, 21:46 +0100 schrieb Marek Vasut:
> > From: Sean Cross <xobs@kosagi.com>
> >
> > Novena is an open-hardware laptop/desktop/bare board.
> >
> > See http://www.kosagi.com/w/index.php?title=Novena_Main_Page
> >
> > Signed-off-by: Sean Cross <xobs@kosagi.com>
> > Cc: Fabio Estevam <fabio.estevam@freescale.com>
> > Cc: Lucas Stach <l.stach@pengutronix.de>
> > Cc: Sean Cross <xobs@kosagi.com>
> > Cc: Shawn Guo <shawnguo@kernel.org>
> > ---
> >
> > arch/arm/boot/dts/Makefile | 1 +
> > arch/arm/boot/dts/imx6q-novena.dts | 856
> > +++++++++++++++++++++++++++++++++++++ 2 files changed, 857
> > insertions(+)
> > create mode 100644 arch/arm/boot/dts/imx6q-novena.dts
> >
> > V2: Fix the PCIe regulator, make it always on
> >
> > Fix the polarity of SD2 WP and CD lines, make them active low.
> > Drop the simple-bus for regulators, put them in /soc instead.
>
> Huh? No. The fixed and GPIO controlled regulators are certainly not part
> of the SoC. They are board level components and belong into the same DT
> hierarchy level as the sound codec and leds.
Huh? When I did that with 4.4rc1, the regulators were not detected, but with
4.4rc2 they are. Must've been some instability at that point of development
cycle. I will test this some more and then send a V3.
Thanks for the help :)
> Otherwise looks good now.
>
> Regards,
> Lucas
Best regards,
Marek Vasut
next prev parent reply other threads:[~2015-11-24 11:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 9:48 [PATCH 1/2] devicetree: bindings: Add vendor prefix for Kosagi Marek Vasut
2015-11-18 9:48 ` [PATCH 2/2] ARM: dts: imx6q: add Novena board Marek Vasut
2015-11-18 10:10 ` Lucas Stach
2015-11-18 10:35 ` Marek Vasut
2015-11-18 11:25 ` Lucas Stach
2015-11-18 11:32 ` Marek Vasut
2015-11-18 11:36 ` Lucas Stach
2015-11-19 16:03 ` Marek Vasut
2015-11-18 12:14 ` Fabio Estevam
2015-11-18 12:00 ` Fabio Estevam
2015-11-19 16:11 ` Marek Vasut
2015-11-20 2:49 ` Sean Cross
2015-11-20 9:07 ` Marek Vasut
2015-11-20 20:46 ` [PATCH V2 " Marek Vasut
2015-11-20 20:58 ` Fabio Estevam
2015-11-20 21:05 ` Marek Vasut
2015-11-23 9:15 ` Lucas Stach
2015-11-24 11:04 ` Marek Vasut [this message]
2015-11-20 21:19 ` [PATCH 1/2] devicetree: bindings: Add vendor prefix for Kosagi Arnd Bergmann
2015-11-20 22:30 ` Marek Vasut
2015-11-20 22:46 ` Arnd Bergmann
2015-11-21 0:08 ` Marek Vasut
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=201511241204.55621.marex@denx.de \
--to=marex@denx.de \
--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;
as well as URLs for NNTP newsgroup(s).