linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Graute <oliver.graute@gmail.com>
To: aisheng.dong@nxp.com
Cc: devicetree@vger.kernel.org, peng.fan@nxp.com,
	Anson.Huang@nxp.com, linux-imx@nxp.com, festevam@gmail.com,
	linux-arm-kernel@lists.infradead.org
Subject: RFC: imx8: imx8qm with LCD Panel on lpspi
Date: Thu, 20 Feb 2020 17:04:41 +0100	[thread overview]
Message-ID: <20200220160441.GC31464@optiplex> (raw)

Hello Aisheng,

I try to get a LCD Panel working with the imx8qm. The Panel is connected
to lpspi. But I'am not sure if I handle the imx8qm clocking the right
way. Should I use the imx7ul compatible or the imx8qxp compatible? Which
clock defines should I use for the SPI1 Clk?

Best Regards,

Oliver


	lpspi1: lpspi@5a010000 {
		compatible = "fsl,imx7ulp-spi";
		/* compatible = "fsl,imx8qxp-spi"; */
		reg = <0x0 0x5a010000 0x0 0x10000>;
		interrupts = <GIC_SPI 217 IRQ_TYPE_LEVEL_HIGH>;
		interrupt-parent = <&gic>;
		clocks = <&clk IMX_ADMA_SPI1_CLK>,
		         <&clk IMX_IMG_IPG_CLK>;
		clock-names = "per", "ipg";
		assigned-clocks = <&clk IMX_ADMA_SPI1_CLK>;
		assigned-clock-rates = <20000000>;
		status = "disabled";
	};

&lpspi1 {
	#address-cells = <1>;
	#size-cells = <0>;
	fsl,spi-num-chipselects = <1>;
	pinctrl-names = "default";
	pinctrl-0 = <&pinctrl_lpspi1 &pinctrl_lpspi1_cs>;
	cs-gpios = <&lsio_gpio3 24 GPIO_ACTIVE_LOW>;
	status = "okay";

	panel@0 {
		compatible = "sitronix,st7789v";
		reg = <0>;

		/* reset-gpios = <&lsio_gpio3 11 GPIO_ACTIVE_LOW>; */

		backlight = <&lvds_backlight1>;
		spi-max-frequency = <30000000>;
		spi-cpol;
		spi-cpha;

		port {
			panel_input: endpoint {
				remote-endpoint = <&tcon0_out_panel>;
			};
		};

	};
};

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

                 reply	other threads:[~2020-02-21  6:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200220160441.GC31464@optiplex \
    --to=oliver.graute@gmail.com \
    --cc=Anson.Huang@nxp.com \
    --cc=aisheng.dong@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=peng.fan@nxp.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).