From: Shawn Guo <shawnguo@kernel.org>
To: Ivan Bornyakov <i.bornyakov@metrotek.ru>
Cc: system@metrotek.ru, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 0/2] bus: imx-weim: optionally enable continuous burst clock
Date: Tue, 14 Dec 2021 10:35:53 +0800 [thread overview]
Message-ID: <20211214023553.GM4216@dragon> (raw)
In-Reply-To: <20211202055724.4416-1-i.bornyakov@metrotek.ru>
On Thu, Dec 02, 2021 at 08:57:22AM +0300, Ivan Bornyakov wrote:
> Introduce option to enable continuous burst clock, if burst clock itself
> is enabled.
>
> Changelog:
> v1 -> v2:
> * documentation about this option added to
> Documentation/devicetree/bindings/bus/imx-weim.txt
> v2 -> v3:
> * added missing Signed-off-by line
>
>
> Ivan Bornyakov (2):
> bus: imx-weim: optionally enable continuous burst clock
> dt-bindings: bus: imx-weim: add words about continuous bclk
Applied both, thanks!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-12-14 2:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 5:57 [PATCH v3 0/2] bus: imx-weim: optionally enable continuous burst clock Ivan Bornyakov
2021-12-02 5:57 ` [PATCH v3 1/2] " Ivan Bornyakov
2021-12-02 5:57 ` [PATCH v3 2/2] dt-bindings: bus: imx-weim: add words about continuous bclk Ivan Bornyakov
2021-12-10 22:13 ` Rob Herring
2021-12-09 6:10 ` [PATCH v3 0/2] bus: imx-weim: optionally enable continuous burst clock Ivan Bornyakov
2021-12-14 2:35 ` Shawn Guo [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=20211214023553.GM4216@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--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=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).