From: "Sören Brinkmann" <soren.brinkmann@xilinx.com>
To: Ranjit Waghmode <ranjit.waghmode@xilinx.com>
Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
michal.simek@xilinx.com, corbet@lwn.net, lars@metafoo.de,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, punnaia@xilinx.com,
anirudh@xilinx.com
Subject: Re: [RFC LINUX PATCH] dt: xilinx: xadc: provision to control clock frequency
Date: Wed, 23 Dec 2015 03:49:08 -0800 [thread overview]
Message-ID: <20151223114908.GG6491@xsjsorenbubuntu> (raw)
In-Reply-To: <1450866505-22069-1-git-send-email-ranjit.waghmode@xilinx.com>
On Wed, 2015-12-23 at 03:58PM +0530, Ranjit Waghmode wrote:
> This patch adds parameter to the xilinx-xadc node for controlling
> clock frequency.
>
> Following are the possible options for user to control the frequency:
> * 00 : 1/2 of clock frequency
> * 01 : 1/4 of clock frequency
> * 10 : 1/8 of clock frequency
> * 11 : 1/16 of clock frequency
How is this chosen? Are these just arbitrary values that you need for
some use-case? Or are these the options HW allows?
>
> So this patch adds parameter tck-rate to set user defined values from
> above pool to control the clock frequency.
This is no longer describing HW, but configuring driver/HW. Why does
this have to be in DT? Why can't the driver request/set the frequency as
operation requires it?
Thanks,
Sören
prev parent reply other threads:[~2015-12-23 11:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 10:28 [RFC LINUX PATCH] dt: xilinx: xadc: provision to control clock frequency Ranjit Waghmode
2015-12-23 11:49 ` Sören Brinkmann [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=20151223114908.GG6491@xsjsorenbubuntu \
--to=soren.brinkmann@xilinx.com \
--cc=anirudh@xilinx.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=pawel.moll@arm.com \
--cc=punnaia@xilinx.com \
--cc=ranjit.waghmode@xilinx.com \
--cc=robh+dt@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