u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: Zhengxun Li <zhengxunli.mxic@gmail.com>
To: Sean Anderson <sean.anderson@seco.com>
Cc: u-boot@lists.denx.de, Michal Simek <michal.simek@xilinx.com>,
	lukma@denx.de, zhengxunli@mxic.com.tw
Subject: Re: [PATCH v6 2/2] dt-bindings: add xilinx clocking wizard bindings
Date: Tue, 15 Jun 2021 17:21:11 +0000	[thread overview]
Message-ID: <CACY_kjQ_C+qrYgK0ukzx-n1bCKoSOfwrfOvwxbtqDcughSHJ4A@mail.gmail.com> (raw)
In-Reply-To: <40fad673-536b-374c-af15-70616ffa6745@seco.com>

Hi Michal,

Sean Anderson <sean.anderson@seco.com> 於 2021年6月11日 週五 下午3:07寫道：
>
>
>
> On 6/11/21 11:10 AM, Zhengxun wrote:
>  > Add the devicetree binding for the xilinx clocking wizard.
>  >
>  > Signed-off-by: Zhengxun <zhengxunli.mxic@gmail.com>
>  > ---
>  >   .../clock/xlnx,clocking-wizard.txt            | 43 +++++++++++++++++++
>  >   1 file changed, 43 insertions(+)
>  >   create mode 100644 doc/device-tree-bindings/clock/xlnx,clocking-wizard.txt
>
> Should this be .yml? In general, I believe we only need to document
> bindings in U-Boot if they differ from Linux. In Linux, I see that
> Documentation/devicetree/bindings/clock/xlnx,clocking-wizard.txt exists.
> Will you be upstreaming this conversion to yaml?

Can you give some suggestions?

Thanks,
Zhengxun

  reply	other threads:[~2021-06-15  9:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-11 15:10 [PATCH v6 0/2] Add Xilinx clock wizard driver support Zhengxun
2021-06-11 15:10 ` [PATCH v6 1/2] clk: zynq: Add clock wizard driver Zhengxun
2021-06-11 15:09   ` Sean Anderson
2021-06-16 10:01   ` Michal Simek
2021-06-11 15:10 ` [PATCH v6 2/2] dt-bindings: add xilinx clocking wizard bindings Zhengxun
2021-06-11 15:07   ` Sean Anderson
2021-06-15 17:21     ` Zhengxun Li [this message]
2021-06-15 14:52       ` Sean Anderson
2021-06-16 15:26         ` Zhengxun Li
2021-06-16 10:04           ` Michal Simek
2021-06-17 11:12             ` Zhengxun Li

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=CACY_kjQ_C+qrYgK0ukzx-n1bCKoSOfwrfOvwxbtqDcughSHJ4A@mail.gmail.com \
    --to=zhengxunli.mxic@gmail.com \
    --cc=lukma@denx.de \
    --cc=michal.simek@xilinx.com \
    --cc=sean.anderson@seco.com \
    --cc=u-boot@lists.denx.de \
    --cc=zhengxunli@mxic.com.tw \
    /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).