From: Greg KH <gregkh@linuxfoundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Christian Gromm <christian.gromm@microchip.com>,
Rob Herring <robh+dt@kernel.org>,
Nikita Yushchenko <nikita.yoush@cogentembedded.com>,
linux-staging@lists.linux.dev, devicetree@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 23/28] staging: most: dim2: use device tree
Date: Wed, 13 Oct 2021 14:24:49 +0200 [thread overview]
Message-ID: <YWbQEQBYTrfmzq4N@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2110121749450.1045463@ramsan.of.borg>
On Tue, Oct 12, 2021 at 08:14:14PM +0200, Geert Uytterhoeven wrote:
> Hi Christian, Greg,
>
> CC devicetree, linux-renesas-soc
>
> On Tue, 8 May 2018, Christian Gromm wrote:
> > This patch removes the dependency to platform specific source files
> > that do platform specific initialization and supply the IRQ number.
> > Instead DT code is added
> >
> > Signed-off-by: Christian Gromm <christian.gromm@microchip.com>
>
> This patch bypassed review by the DT people, and ended up in v4.18 as
> commit 21e57ff086056c01 ("staging: most: dim2: use device tree").
Yeah, staging-only dt changes are not usually run by the dt maintainers.
>
> > --- a/drivers/staging/most/dim2/dim2.c
> > +++ b/drivers/staging/most/dim2/dim2.c
> > +static const struct of_device_id dim2_of_match[] = {
> > + {
> > + .compatible = "fsl,imx6q-mlb150",
> > + .data = plat_data + FSL_MX6
> > + },
> > + {
> > + .compatible = "renesas,mlp",
> > + .data = plat_data + RCAR_H2
> > + },
> > + {
> > + .compatible = "rcar,medialb-dim2",
> > + .data = plat_data + RCAR_M3
> > + },
> > + {
> > + .compatible = "xlnx,axi4-os62420_3pin-1.00.a",
> > + },
> > + {
> > + .compatible = "xlnx,axi4-os62420_6pin-1.00.a",
> > + },
> > + {},
> > };
>
> There are no documented DT bindings for this hardware block, nor any
> upstream example users. Given some compatible values do not follow
> standard practises (no idea about the other parts), it's very likely
> these de facto bindings, and all their out-of-tree users, will have to
> be changed.
Great, fix the bindings and anything in-kernel here please. We don't
care about out-of-kernel stuff for drivers/staging/ at all.
thanks,
greg k-h
prev parent reply other threads:[~2021-10-13 12:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1525772716-15742-1-git-send-email-christian.gromm@microchip.com>
[not found] ` <1525772716-15742-24-git-send-email-christian.gromm@microchip.com>
2021-10-12 18:14 ` [PATCH 23/28] staging: most: dim2: use device tree Geert Uytterhoeven
2021-10-13 12:24 ` Greg KH [this message]
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=YWbQEQBYTrfmzq4N@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=christian.gromm@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=nikita.yoush@cogentembedded.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).