From: Philipp Rossak <embed3d@gmail.com>
To: Sergey Suloev <ssuloev@orpaltech.com>,
robh+dt@kernel.org, mark.rutland@arm.com, linux@armlinux.org.uk,
maxime.ripard@free-electrons.com, wens@csie.org
Cc: devicetree@vger.kernel.org, linux-sunxi@googlegroups.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] Fix broken bananapi m2 devicetree/regulators
Date: Sat, 10 Feb 2018 23:07:01 +0100 [thread overview]
Message-ID: <da8909da-4eea-0fdf-e104-4442f7986455@gmail.com> (raw)
In-Reply-To: <40887d4b-0fb0-239e-e5a9-1a87f82946c2@orpaltech.com>
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-test-2
next prev parent reply other threads:[~2018-02-10 22:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 17:52 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 [this message]
2018-02-11 7:29 ` Sergey Suloev
2018-02-11 7:55 ` Sergey Suloev
2018-02-11 11:30 ` Philipp Rossak
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=da8909da-4eea-0fdf-e104-4442f7986455@gmail.com \
--to=embed3d@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=robh+dt@kernel.org \
--cc=ssuloev@orpaltech.com \
--cc=wens@csie.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
Powered by JetHome