From: Tony Lindgren <tony@atomide.com>
To: "Derald D. Woods" <woods.technical@gmail.com>
Cc: linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/4] ARM: dts: omap3: Fix Sharp LS037V7DW01 compatible string and envdd supply
Date: Tue, 12 Sep 2017 07:34:46 -0700 [thread overview]
Message-ID: <20170912143444.GR5024@atomide.com> (raw)
In-Reply-To: <20170912034659.13184-4-woods.technical@gmail.com>
* Derald D. Woods <woods.technical@gmail.com> [170911 20:48]:
> The Sharp panel driver and regulator are now selected properly. This
> commit eliminates a dummy regulator assignment.
>
> Signed-off-by: Derald D. Woods <woods.technical@gmail.com>
>
> ---
> arch/arm/boot/dts/omap3-panel-sharp-ls037v7dw01.dtsi | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/omap3-panel-sharp-ls037v7dw01.dtsi b/arch/arm/boot/dts/omap3-panel-sharp-ls037v7dw01.dtsi
> index 157345bb8e79..15f73e5adfdf 100644
> --- a/arch/arm/boot/dts/omap3-panel-sharp-ls037v7dw01.dtsi
> +++ b/arch/arm/boot/dts/omap3-panel-sharp-ls037v7dw01.dtsi
> @@ -26,9 +26,10 @@
> };
>
> lcd0: display {
> - compatible = "sharp,ls037v7dw01";
> + compatible = "omapdss,sharp,ls037v7dw01";
Is this change needed? I think the driver automatically matches
even with the "omapdss" part missing?
If it's needed, can you please update the description for why
it's needed.
Regards,
Tony
next prev parent reply other threads:[~2017-09-12 14:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-03 0:38 [PATCH 0/2] Update TMDSEVM3530 support for omap3-evm Derald D. Woods
2017-09-03 0:38 ` [PATCH 1/2] ARM: dts: omap3-evm-37xx: Add common processor module support Derald D. Woods
2017-09-03 0:38 ` [PATCH 2/2] ARM: dts: omap3-evm: Add OMAP3530 specific device tree processor data Derald D. Woods
2017-09-05 16:49 ` [PATCH 0/2] Update TMDSEVM3530 support for omap3-evm Tony Lindgren
2017-09-12 3:46 ` [PATCH v2 0/4] " Derald D. Woods
2017-09-12 3:46 ` [PATCH v2 1/4] ARM: dts: omap3-evm-37xx: Add common processor module support Derald D. Woods
2017-09-12 3:46 ` [PATCH v2 2/4] ARM: dts: omap3-evm: Add OMAP3530 specific device tree processor data Derald D. Woods
2017-09-12 3:46 ` [PATCH v2 3/4] ARM: dts: omap3: Fix Sharp LS037V7DW01 compatible string and envdd supply Derald D. Woods
2017-09-12 14:34 ` Tony Lindgren [this message]
2017-09-12 17:33 ` Derald D. Woods
2017-09-12 3:46 ` [PATCH v2 4/4] ARM: dts: omap3-evm: Add DSS {vdds_dsi,vdda_video}-supply references Derald D. Woods
2017-09-12 23:48 ` [PATCH v3 0/4] Update TMDSEVM3530 support for omap3-evm Derald D. Woods
2017-09-12 23:48 ` [PATCH v3 1/4] ARM: dts: omap3-evm-37xx: Add common processor module support Derald D. Woods
2017-09-12 23:48 ` [PATCH v3 2/4] ARM: dts: omap3-evm: Add OMAP3530 specific device tree processor data Derald D. Woods
2017-09-12 23:48 ` [PATCH v3 3/4] ARM: dts: omap3: Add Sharp LS037V7DW01 'envdd' supply Derald D. Woods
2017-09-12 23:48 ` [PATCH v3 4/4] ARM: dts: omap3-evm: Add DSS {vdds_dsi,vdda_video}-supply references Derald D. Woods
2017-09-29 2:04 ` [PATCH v3 0/4] Update TMDSEVM3530 support for omap3-evm Derald D. Woods
2017-09-29 16:20 ` Tony Lindgren
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=20170912143444.GR5024@atomide.com \
--to=tony@atomide.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=woods.technical@gmail.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