From: jbrunet@baylibre.com (Jerome Brunet)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH] nvmem: meson: use generic compatible
Date: Fri, 13 Oct 2017 21:39:13 +0200 [thread overview]
Message-ID: <1507923553.30658.10.camel@baylibre.com> (raw)
In-Reply-To: <CAFBinCBVNEqTk+NUHz62FetLhYagFb5K+g17P_2Xb7sBUfEmdA@mail.gmail.com>
On Fri, 2017-10-13 at 21:14 +0200, Martin Blumenstingl wrote:
> Hi Jerome,
>
> On Thu, Oct 12, 2017 at 5:24 PM, Jerome Brunet <jbrunet@baylibre.com> wrote:
> > The meson efuse driver seems to be compatible with more SoCs than
> > initially thought. Let's use the most generic compatible he have in
> > DT instead of the gxbb specific one
> >
> > Signed-off-by: Jerome Brunet <jbrunet@baylibre.com>
> > ---
> > Documentation/devicetree/bindings/nvmem/amlogic-efuse.txt | 4 ++--
> > drivers/nvmem/meson-efuse.c | 2 +-
> > 2 files changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/nvmem/amlogic-efuse.txt
> > b/Documentation/devicetree/bindings/nvmem/amlogic-efuse.txt
> > index fafd85bd67a6..0260524292fe 100644
> > --- a/Documentation/devicetree/bindings/nvmem/amlogic-efuse.txt
> > +++ b/Documentation/devicetree/bindings/nvmem/amlogic-efuse.txt
> > @@ -1,7 +1,7 @@
> > = Amlogic eFuse device tree bindings =
> >
> > Required properties:
> > -- compatible: should be "amlogic,meson-gxbb-efuse"
> > +- compatible: should be "amlogic,meson-gx-efuse"
>
> have you checked with the devicetree maintainers how they want the
> documentation to look like in this case?
You mean "Should we put every compatible existing (in DT) in the documentation"
>From what I've seen, at least in meson drivers, only the matched ones are
listed.
That's a good question though.
We tend to put soc specific compatible "in case" we need them later on. Should
we document those ?
> (I don't know if the old one should be kept instead of removing it)
>
> >
> > = Data cells =
> > Are child nodes of eFuse, bindings of which as described in
> > @@ -10,7 +10,7 @@ bindings/nvmem/nvmem.txt
> > Example:
> >
> > efuse: efuse {
> > - compatible = "amlogic,meson-gxbb-efuse";
> > + compatible = "amlogic,meson-gx-efuse";
> > #address-cells = <1>;
> > #size-cells = <1>;
> >
> > diff --git a/drivers/nvmem/meson-efuse.c b/drivers/nvmem/meson-efuse.c
> > index 70bfc9839bb2..e90c6d68a263 100644
> > --- a/drivers/nvmem/meson-efuse.c
> > +++ b/drivers/nvmem/meson-efuse.c
> > @@ -44,7 +44,7 @@ static struct nvmem_config econfig = {
> > };
> >
> > static const struct of_device_id meson_efuse_match[] = {
> > - { .compatible = "amlogic,meson-gxbb-efuse", },
> > + { .compatible = "amlogic,meson-gx-efuse", },
> > { /* sentinel */ },
> > };
> > MODULE_DEVICE_TABLE(of, meson_efuse_match);
> > --
> > 2.13.6
> >
> >
> > _______________________________________________
> > linux-amlogic mailing list
> > linux-amlogic at lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2017-10-13 19:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 15:24 [PATCH] nvmem: meson: use generic compatible Jerome Brunet
2017-10-13 19:14 ` Martin Blumenstingl
2017-10-13 19:39 ` Jerome Brunet [this message]
2017-10-17 20:52 ` Rob Herring
2017-10-18 7:31 ` Jerome Brunet
2017-10-19 21:10 ` Rob Herring
2017-10-20 8:21 ` Jerome Brunet
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=1507923553.30658.10.camel@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=linus-amlogic@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