Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1297396
| From | Sören Brinkmann <soren.brinkmann@xilinx.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC LINUX PATCH] dt: xilinx: xadc: provision to control clock frequency |
| Date | 2015-12-23 12:50 +0100 |
| Message-ID | <qIQ5A-Cl-3@gated-at.bofh.it> (permalink) |
| References | <qIOQc-8nu-49@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[RFC LINUX PATCH] dt: xilinx: xadc: provision to control clock frequency Ranjit Waghmode <ranjit.waghmode@xilinx.com> - 2015-12-23 11:30 +0100 Re: [RFC LINUX PATCH] dt: xilinx: xadc: provision to control clock frequency Sören Brinkmann <soren.brinkmann@xilinx.com> - 2015-12-23 12:50 +0100
csiph-web