From: Fabio Estevam <festevam@gmail.com>
To: Ivan Bornyakov <i.bornyakov@metrotek.ru>
Cc: system@metrotek.ru, Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Sascha Hauer <kernel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] bus: imx-weim: optionally enable continuous burst clock
Date: Sat, 11 Dec 2021 08:04:00 -0300 [thread overview]
Message-ID: <CAOMZO5CLRaFhd31Q4LaFt+R4sNiAmZ6rg0BzjBmWow779OnWCA@mail.gmail.com> (raw)
In-Reply-To: <20211124175542.2772-2-i.bornyakov@metrotek.ru>
On Wed, Nov 24, 2021 at 3:10 PM Ivan Bornyakov <i.bornyakov@metrotek.ru> wrote:
>
> To enable continuous burst clock, add "fsl,continuous-burst-clk" along
> with "fsl,burst-clk-enable" property to the weim bus's devicetree node.
>
> Example:
> weim: weim@21b8000 {
> compatible = "fsl,imx6ul-weim", "fsl,imx6q-weim";
> reg = <0x021b8000 0x4000>;
> clocks = <&clks 143>;
> #address-cells = <2>;
> #size-cells = <1>;
> ranges = <0 0 0x50000000 0x08000000>;
> fsl,weim-cs-gpr = <&gpr>;
> fsl,burst-clk-enable;
> fsl,continuous-burst-clk;
>
> client-device@0 {
> ...
> };
> };
>
> Signed-off-by: Ivan Bornyakov <i.bornyakov@metrotek.ru>
Reviewed-by: Fabio Estevam <festevam@gmail.com>
next prev parent reply other threads:[~2021-12-11 11:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 17:55 [PATCH v2 0/2] bus: imx-weim: optionally enable continuous burst clock Ivan Bornyakov
2021-11-24 17:55 ` [PATCH v2 1/2] " Ivan Bornyakov
2021-12-11 11:04 ` Fabio Estevam [this message]
2021-11-24 17:55 ` [PATCH v2 2/2] dt-bindings: bus: imx-weim: add words about continuous bclk Ivan Bornyakov
2021-12-01 22:17 ` Rob Herring
2021-12-01 10:25 ` [PATCH v2 0/2] bus: imx-weim: optionally enable continuous burst clock Ivan Bornyakov
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=CAOMZO5CLRaFhd31Q4LaFt+R4sNiAmZ6rg0BzjBmWow779OnWCA@mail.gmail.com \
--to=festevam@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=i.bornyakov@metrotek.ru \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=system@metrotek.ru \
/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).