From: embed3d@gmail.com (Philipp Rossak)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Fix broken bananapi m2 devicetree/regulators
Date: Sun, 11 Feb 2018 12:30:31 +0100 [thread overview]
Message-ID: <1518348631.1342.1.camel@gmail.com> (raw)
In-Reply-To: <45fb86c9-2218-d00d-1952-6b79f9101049@orpaltech.com>
Am Sonntag, den 11.02.2018, 10:55 +0300 schrieb Sergey Suloev:
> On 02/11/2018 01:07 AM, Philipp Rossak wrote:
> >
> >
> > On 10.02.2018 22:08, Sergey Suloev wrote:
> > > On 02/11/2018 12:01 AM, Philipp Rossak wrote:
> > > > Hey Sergey,
> > > >
> > > > Thanks for mentioning, but I think the problem has nothing to
> > > > do?
> > > > with those patches. I tested them with the v4.15.0 Kernel since
> > > > this?
> > > > is the last stable release and we are right now in the merging
> > > > window.
> > > >
> > > > I tested the latest mainline, without those patches and the
> > > > kernel?
> > > > is not booting (I can't see any uart output).
> > > >
> > > > Thanks,
> > > > Philipp
> > > >
> > > > On 10.02.2018 14:56, Sergey Suloev wrote:
> > > > > On 02/09/2018 08:52 PM, Philipp Rossak wrote:
> > > > > > This patchseries fixes the bananapi m1 devicetree, to be
> > > > > > able to?
> > > > > > boot again.
> > > > > > The first two patches update/improve the devicetree and the
> > > > > > last?
> > > > > > patch adds
> > > > > > all missing regulators.
> > > > > >
> > > > > > Regards,
> > > > > > Philipp
> > > > > >
> > > > > > Philipp Rossak (3):
> > > > > > ?? arm: dts: sun6i: a31s: bpi-m2: update mmc supply nodes
> > > > > > ?? arm: dts: sun6i: a31s: bpi-m2: improve pmic properties
> > > > > > ?? arm: dts: sun6i: a31s: fix: bpi-m2: add missing
> > > > > > regulators
> > > > > >
> > > > > > ? arch/arm/boot/dts/sun6i-a31s-sinovoip-bpi-m2.dts | 70?
> > > > > > +++++++++++++++++++++++-
> > > > > > ? 1 file changed, 67 insertions(+), 3 deletions(-)
> > > > > >
> > > > >
> > > > > patches are not working
> > > > >
> > > > > Thanks
> > > > >
> > >
> > > same problem, but after applying the patches my device is till
> > > hanging.
> > >
> > >
> >
> > Can you please share a bootlog? Here is mine [1]. As you can see
> > I'm?
> > able to boot.
> > I build it with this branch [2]. For testing you should replace
> > the?
> > dtb and the uImage/zImage
> >
> > Philipp
> >
> >
> > [1]: https://pastebin.com/mVjv3LDf
> > [2]:?
> > https://github.com/embed-3d/linux/tree/testing/bpi-m2-regulator-tes
> > t-2
>
> My dmesg is very similar to yours unless it hangs on the last line
> [1].?
> For this test I used kernel from tag v4.15 with no additional
> patching.
>
> [1] https://pastebin.com/3a6bk5Dk
>
>
For me it looks like you have a different kernel and also an different
dtb that you patch! And you are applying also a fixup script.
These patches should be applied on top of linux mainline.
fixup script:
Applying kernel provided DT fixup script (sun6i-a31s-fixup.scr)
Linux versions:
4.15.0-00003-g1bbe5edde691 vs 4.15.0-sunxi-dirty
In addition to that you are also booting into fb/hdmi.
If you use my branch (uImage and dtb) and replace the current boot.cmd
with this (to get the boot.scr you need to use mkimage) it should work:
setenv bootargs console=ttyS0,115200 root=/dev/mmcblk0p2 rw rootwait
panic=10
load mmc 0:1 0x43000000 ${fdtfile} || load mmc 0:1 0x43000000
boot/${fdtfile}
load mmc 0:1 0x42000000 uImage || load mmc 0:1 0x42000000 boot/uImage
bootm 0x42000000 - 0x43000000
next prev parent reply other threads:[~2018-02-11 11:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 17:52 [PATCH 0/3] Fix broken bananapi m2 devicetree/regulators Philipp Rossak
2018-02-09 17:52 ` [PATCH 1/3] arm: dts: sun6i: a31s: bpi-m2: update mmc supply nodes Philipp Rossak
2018-02-11 22:15 ` Philipp Rossak
2018-02-09 17:52 ` [PATCH 2/3] arm: dts: sun6i: a31s: bpi-m2: improve pmic properties Philipp Rossak
2018-02-09 17:52 ` [PATCH 3/3] arm: dts: sun6i: a31s: fix: bpi-m2: add missing regulators Philipp Rossak
2018-02-10 13:56 ` [PATCH 0/3] Fix broken bananapi m2 devicetree/regulators Sergey Suloev
2018-02-10 21:01 ` Philipp Rossak
2018-02-10 21:08 ` Sergey Suloev
2018-02-10 22:07 ` Philipp Rossak
2018-02-11 7:29 ` Sergey Suloev
2018-02-11 7:55 ` Sergey Suloev
2018-02-11 11:30 ` Philipp Rossak [this message]
2018-02-11 11:36 ` Sergey Suloev
2018-02-11 11:44 ` Sergey Suloev
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=1518348631.1342.1.camel@gmail.com \
--to=embed3d@gmail.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;
as well as URLs for NNTP newsgroup(s).