Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1588151
| From | Sakari Ailus <sakari.ailus@iki.fi> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v9 1/2] Add OV5647 device tree documentation |
| Date | 2017-02-25 16:40 +0100 |
| Message-ID | <teMBY-1sj-5@gated-at.bofh.it> (permalink) |
| References | (3 earlier) <tdp4K-7un-15@gated-at.bofh.it> <tdpxL-7Jl-9@gated-at.bofh.it> <tdqtP-8mV-3@gated-at.bofh.it> <tdrgf-sR-35@gated-at.bofh.it> <teMiC-1iP-19@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Sat, Feb 25, 2017 at 04:50:53PM +0200, Sakari Ailus wrote: > Although, the driver could try to work on the actual obtained frequency. > This is unlikely to work though, but it won't be very easy to figure out > why the device isn't working. Having the frequency in DT accessible for the > driver to check makes failing early with a clear error message possible. The below point actually makes the above matter a non-issue: this driver will contain a list of supported frequencies. A SMIA driver that I typically work with, for instance, does not. So I think your suggestion of having the CCF handle setting the frequency is a good one. > > > > > So, the clock frequency set up is delegated to CCF, and when any other > > than 25 MHz frequencies are got supported, that's only the matter of > > driver updates, DTBs won't be touched. > > Indeed. The new supported frequencies in this case will be additional > single values; there won't be ranges or such. The register lists the > driver contains are more or less dependent on that frequency. -- Kind regards, Sakari Ailus e-mail: sakari.ailus@iki.fi XMPP: sailus@retiisi.org.uk
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[PATCH v9 1/2] Add OV5647 device tree documentation Ramiro Oliveira <Ramiro.Oliveira@synopsys.com> - 2017-02-17 14:20 +0100
Re: [PATCH v9 1/2] Add OV5647 device tree documentation Sakari Ailus <sakari.ailus@iki.fi> - 2017-02-21 13:00 +0100
Re: [PATCH v9 1/2] Add OV5647 device tree documentation Ramiro Oliveira <Ramiro.Oliveira@synopsys.com> - 2017-02-21 15:40 +0100
Re: [PATCH v9 1/2] Add OV5647 device tree documentation Sakari Ailus <sakari.ailus@iki.fi> - 2017-02-21 15:50 +0100
Re: [PATCH v9 1/2] Add OV5647 device tree documentation Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com> - 2017-02-21 17:00 +0100
Re: [PATCH v9 1/2] Add OV5647 device tree documentation Ramiro Oliveira <Ramiro.Oliveira@synopsys.com> - 2017-02-21 21:20 +0100
Re: [PATCH v9 1/2] Add OV5647 device tree documentation Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com> - 2017-02-21 21:50 +0100
Re: [PATCH v9 1/2] Add OV5647 device tree documentation Sakari Ailus <sakari.ailus@iki.fi> - 2017-02-21 22:50 +0100
Re: [PATCH v9 1/2] Add OV5647 device tree documentation Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com> - 2017-02-21 23:40 +0100
Re: [PATCH v9 1/2] Add OV5647 device tree documentation Ramiro Oliveira <Ramiro.Oliveira@synopsys.com> - 2017-02-22 12:00 +0100
Re: [PATCH v9 1/2] Add OV5647 device tree documentation Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com> - 2017-02-22 12:50 +0100
Re: [PATCH v9 1/2] Add OV5647 device tree documentation Ramiro Oliveira <Ramiro.Oliveira@synopsys.com> - 2017-02-22 15:50 +0100
Re: [PATCH v9 1/2] Add OV5647 device tree documentation Sakari Ailus <sakari.ailus@iki.fi> - 2017-02-25 16:20 +0100
Re: [PATCH v9 1/2] Add OV5647 device tree documentation Sakari Ailus <sakari.ailus@iki.fi> - 2017-02-25 16:40 +0100
csiph-web