devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: Maciej Purski <m.purski@samsung.com>
Cc: Mark Brown <broonie@kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>, Liam Girdwood <lgirdwood@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Doug Anderson <dianders@chromium.org>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: [PATCH v5 0/5] Add coupled regulators mechanism
Date: Mon, 5 Mar 2018 12:57:39 -0300	[thread overview]
Message-ID: <CAOMZO5Cdg4Njd5kXT4tqnJngSPr9NNHdSpoqT3UfmHYYpvuj1g@mail.gmail.com> (raw)
In-Reply-To: <6fc780e4-3594-2ca5-dc4e-7e147dc4e40f@samsung.com>

Hi Maciej,

On Mon, Mar 5, 2018 at 11:40 AM, Maciej Purski <m.purski@samsung.com> wrote:
> Hi Fabio,
> thank you for your response.
> Could you tell me on which board precisely (on which DTS) has this issue
> occurred?

I tested it on a imx6dl-wandboard.dtb.

kernelci.org also shows other imx6 boards that cannot boot with
today's linux-next.

> Also, I don't understand, did you boot successfully and you got only a
> lockdep warning or you encountered an actual deadlock?

No, with this series I am not able to boot till the Linux prompt.

Thanks

  reply	other threads:[~2018-03-05 15:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20180302085118eucas1p15a6a5ec5f7f47a6f67a45c5e9495b120@eucas1p1.samsung.com>
2018-03-02  8:42 ` [PATCH v5 0/5] Add coupled regulators mechanism Maciej Purski
     [not found]   ` <CGME20180302085126eucas1p10efa5726623b9b8a31ac438eec9fb726@eucas1p1.samsung.com>
2018-03-02  8:42     ` [PATCH v5 1/5] regulator: bindings: Add properties for coupled regulators Maciej Purski
     [not found]   ` <CGME20180302085127eucas1p11acd79e50c5042b6b9f61c8a8a18011e@eucas1p1.samsung.com>
2018-03-02  8:42     ` [PATCH v5 2/5] regulator: core: Parse coupled regulators properties Maciej Purski
     [not found]   ` <CGME20180302085127eucas1p19293e26a9abe8f7df6936912e6999b3f@eucas1p1.samsung.com>
2018-03-02  8:42     ` [PATCH v5 3/5] regulator: core: Resolve coupled regulators Maciej Purski
     [not found]   ` <CGME20180302085128eucas1p1c8177a8396b555d1fb31207b1fb42b93@eucas1p1.samsung.com>
2018-03-02  8:42     ` [PATCH v5 4/5] regulator: core: Add voltage balancing mechanism Maciej Purski
     [not found]   ` <CGME20180302085129eucas1p165d7e94517ca9c6fee534f53a88125a9@eucas1p1.samsung.com>
2018-03-02  8:42     ` [PATCH v5 5/5] regulator: core: Change voltage setting path Maciej Purski
2018-03-05 12:34   ` [PATCH v5 0/5] Add coupled regulators mechanism Fabio Estevam
2018-03-05 14:40     ` Maciej Purski
2018-03-05 15:57       ` Fabio Estevam [this message]
2018-03-05 19:30         ` Fabio Estevam

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=CAOMZO5Cdg4Njd5kXT4tqnJngSPr9NNHdSpoqT3UfmHYYpvuj1g@mail.gmail.com \
    --to=festevam@gmail.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.purski@samsung.com \
    --cc=m.szyprowski@samsung.com \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.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).