From: Wen He <wen.he_1@nxp.com>
To: Shawn Guo <shawnguo@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Leo Li <leoyang.li@nxp.com>,
"liviu.dudau@arm.com" <liviu.dudau@arm.com>
Subject: RE: [EXT] Re: [v1 3/3] arm64: dts: ls1028a: Add properties node for Display output pixel clock
Date: Mon, 19 Aug 2019 09:52:09 +0000 [thread overview]
Message-ID: <DB7PR04MB51951491600141680A1146FDE2A80@DB7PR04MB5195.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20190819093159.GJ5999@X250>
> -----Original Message-----
> From: Shawn Guo <shawnguo@kernel.org>
> Sent: 2019年8月19日 17:32
> To: Wen He <wen.he_1@nxp.com>
> Cc: Rob Herring <robh+dt@kernel.org>; Michael Turquette
> <mturquette@baylibre.com>; Stephen Boyd <sboyd@kernel.org>; Mark
> Rutland <mark.rutland@arm.com>; devicetree@vger.kernel.org;
> linux-clk@vger.kernel.org; linux-kernel@vger.kernel.org; Leo Li
> <leoyang.li@nxp.com>; liviu.dudau@arm.com
> Subject: [EXT] Re: [v1 3/3] arm64: dts: ls1028a: Add properties node for
> Display output pixel clock
>
>
> On Mon, Aug 12, 2019 at 06:02:24PM +0800, Wen He wrote:
> > The LS1028A has a clock domain PXLCLK0 used for the Display output
> > interface in the display core, independent of the system bus
> > frequency, for flexible clock design. This display core has its own pixel clock.
> >
> > This patch enable the pixel clock provider on the LS1028A.
> >
> > Signed-off-by: Wen He <wen.he_1@nxp.com>
>
> Applied, thanks.
Thank you for the review, Shawn.
Best Regards,
Wen
prev parent reply other threads:[~2019-08-19 9:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 10:02 [v1 3/3] arm64: dts: ls1028a: Add properties node for Display output pixel clock Wen He
2019-08-19 9:32 ` Shawn Guo
2019-08-19 9:52 ` Wen He [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=DB7PR04MB51951491600141680A1146FDE2A80@DB7PR04MB5195.eurprd04.prod.outlook.com \
--to=wen.he_1@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=shawnguo@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).