From: Adrien Grassein <adrien.grassein@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Jagan Teki <jagan@amarulasolutions.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
DTML <devicetree@vger.kernel.org>, Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v3 3/6] regulator: dt-bindings: pf8x00: remove nxp,ilim-ma property
Date: Mon, 11 Jan 2021 18:27:52 +0100 [thread overview]
Message-ID: <CABkfQAGUkUwS9UKOVY5xP2UYc+zUHL=t7EMPYWTyQ_Pw-v3TOA@mail.gmail.com> (raw)
In-Reply-To: <20210111172019.GH4728@sirena.org.uk>
Hello,
Is there a way to declare it deprecated in the DTB ?
I never saw a deprecated value.
Thanks,
Le lun. 11 janv. 2021 à 18:20, Mark Brown <broonie@kernel.org> a écrit :
>
> On Fri, Jan 08, 2021 at 11:50:03PM +0100, Adrien Grassein wrote:
> > This property seems useless because we can use the
> > regulator-max-microamp generic property to do the same
> > and using generic code.
>
> This made it into a kernel release so we should continue to honour it,
> it's fine to deprecate it though.
next prev parent reply other threads:[~2021-01-11 17:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 22:50 [PATCH v3 0/6] Fix issues on pf8x00 driver Adrien Grassein
2021-01-08 22:50 ` [PATCH v3 1/6] regulator: pf8x00: add a doc for the module Adrien Grassein
2021-01-08 22:50 ` [PATCH v3 2/6] regulator: dt-bindings: pf8x00: fix nxp,phase-shift doc Adrien Grassein
2021-01-13 15:28 ` Rob Herring
2021-01-08 22:50 ` [PATCH v3 3/6] regulator: dt-bindings: pf8x00: remove nxp,ilim-ma property Adrien Grassein
2021-01-11 17:20 ` Mark Brown
2021-01-11 17:27 ` Adrien Grassein [this message]
2021-01-11 17:32 ` Mark Brown
2021-01-08 22:50 ` [PATCH v3 4/6] regulator: " Adrien Grassein
2021-01-08 22:50 ` [PATCH v3 5/6] regulator: pf8x00: use linear range for buck 1-6 Adrien Grassein
2021-01-08 22:50 ` [PATCH v3 6/6] regulator: pf8x00: fix nxp,phase-shift Adrien Grassein
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='CABkfQAGUkUwS9UKOVY5xP2UYc+zUHL=t7EMPYWTyQ_Pw-v3TOA@mail.gmail.com' \
--to=adrien.grassein@gmail.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jagan@amarulasolutions.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@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).