From: Vabhav Sharma <vabhav.sharma@nxp.com>
To: sudeep.holla@arm.com, oss@buserror.net,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
robh+dt@kernel.org, mark.rutland@arm.com,
linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org, mturquette@baylibre.com,
sboyd@kernel.org, rjw@rjwysocki.net, viresh.kumar@linaro.org,
linux-clk@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel-owner@vger.kernel.org, catalin.marinas@arm.com,
will.deacon@arm.com, gregkh@linuxfoundation.org, arnd@arndb.de,
kstewart@linuxfoundation.org, yamada.masahiro@socionext.com,
leoyang.li@nxp.com, shawnguo@kernel.org
Cc: linux@armlinux.org.uk, V.Sethi@nxp.com, udit.kumar@nxp.com,
pankaj.bansal@nxp.com, Vabhav Sharma <vabhav.sharma@nxp.com>
Subject: [PATCH v4 2/6] soc/fsl/guts: Add compatible string for LX2160A
Date: Thu, 4 Oct 2018 06:33:47 +0530 [thread overview]
Message-ID: <1538615031-7507-3-git-send-email-vabhav.sharma@nxp.com> (raw)
In-Reply-To: <1538615031-7507-1-git-send-email-vabhav.sharma@nxp.com>
Adding compatible string "lx2160a-dcfg" to
initialize guts driver for lx2160
Signed-off-by: Vabhav Sharma <vabhav.sharma@nxp.com>
---
drivers/soc/fsl/guts.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/soc/fsl/guts.c b/drivers/soc/fsl/guts.c
index 302e0c8..5e1e633 100644
--- a/drivers/soc/fsl/guts.c
+++ b/drivers/soc/fsl/guts.c
@@ -222,6 +222,7 @@ static const struct of_device_id fsl_guts_of_match[] = {
{ .compatible = "fsl,ls1088a-dcfg", },
{ .compatible = "fsl,ls1012a-dcfg", },
{ .compatible = "fsl,ls1046a-dcfg", },
+ { .compatible = "fsl,lx2160a-dcfg", },
{}
};
MODULE_DEVICE_TABLE(of, fsl_guts_of_match);
--
2.7.4
next prev parent reply other threads:[~2018-10-04 13:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 1:03 [PATCH v4 0/6] arm64: dts: NXP: add basic dts file for LX2160A SoC Vabhav Sharma
2018-10-04 1:03 ` [PATCH v4 1/6] dt-bindings: arm64: add compatible for LX2160A Vabhav Sharma
2018-10-04 1:03 ` Vabhav Sharma [this message]
2018-10-04 1:03 ` [PATCH v4 3/6] clk: qoriq: increase array size of cmux_to_group Vabhav Sharma
2018-10-04 1:03 ` [PATCH v4 4/6] clk: qoriq: Add clockgen support for lx2160a Vabhav Sharma
2018-10-04 1:03 ` [PATCH v4 5/6] arm64: dts: add QorIQ LX2160A SoC support Vabhav Sharma
2018-10-08 5:45 ` Shawn Guo
2018-10-15 2:58 ` Vabhav Sharma
2018-10-15 16:48 ` Stephen Boyd
2018-10-25 4:19 ` Vabhav Sharma
2018-10-04 1:03 ` [PATCH v4 6/6] arm64: dts: add LX2160ARDB board support Vabhav Sharma
2018-10-08 5:52 ` Shawn Guo
2018-10-15 2:44 ` Vabhav Sharma
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=1538615031-7507-3-git-send-email-vabhav.sharma@nxp.com \
--to=vabhav.sharma@nxp.com \
--cc=V.Sethi@nxp.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel-owner@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=oss@buserror.net \
--cc=pankaj.bansal@nxp.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=udit.kumar@nxp.com \
--cc=viresh.kumar@linaro.org \
--cc=will.deacon@arm.com \
--cc=yamada.masahiro@socionext.com \
/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).