Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
1 年多 前同步成功

通知 160
Star 36
Fork 7
cloud-kernel
cloud-kernel
切换分支/标签
  1. 16 1月, 2006 1 次提交
    • H
      V4L/DVB (3384): Separate tv & radio freqs, fix cb/freq transmit order for tuners that need this. · 27487d44
      由 Hans Verkuil 提交于 
      - Moved MSP_SET_MATRIX to v4l2-common.h
- Fix typos and integer overflows in tea5767.c
- Split old freq field into a tv_freq and a radio_freq. Prevents
  that a radio tuner is initialized with a tv frequency or vice versa.
- When switching to radio mode initialize the tuner with the last
  used radio frequency (this was already done for the TV mode).
  As a result of these changes the tuner module now remembers the
  last set radio and TV frequencies, which is what you would expect
  to happen.
- Move out of range frequencies to the closest valid frequency as per
  v4l2 API spec.
- Fix incorrect initial radio frequency (multiplier is 16000, not 16)
- Add boundary check for out of range frequencies.
- Use new flag to check if the order of the CB and freq. depends on
  the last set frequency. That is needed for some tuners or you can
  get static as a result. The flag is added for those tuners where I know
  that the datasheet indicates that this is necessary.
- For this new check use the last set div value, not the last frequency
  as radio frequencies are always much higher due to the 16000 multiplier.
Signed-off-by: NHans Verkuil <hverkuil@xs4all.nl>
Signed-off-by: NMauro Carvalho Chehab <mchehab@infradead.org>
      27487d44
  3. 12 1月, 2006 2 次提交
  5. 10 1月, 2006 6 次提交
  7. 06 1月, 2006 4 次提交
  9. 14 11月, 2005 1 次提交
  11. 09 11月, 2005 12 次提交
  13. 29 10月, 2005 1 次提交
  15. 10 9月, 2005 2 次提交
  17. 06 9月, 2005 1 次提交
  19. 05 9月, 2005 1 次提交
  21. 02 8月, 2005 1 次提交
  23. 16 7月, 2005 1 次提交
  25. 13 7月, 2005 1 次提交
  27. 29 6月, 2005 1 次提交
  29. 24 6月, 2005 3 次提交
  31. 22 6月, 2005 1 次提交
    • J
      [PATCH] I2C: Kill address ranges in non-sensors i2c chip drivers · b3d5496e
      由 Jean Delvare 提交于 
      Some months ago, you killed the address ranges mechanism from all
sensors i2c chip drivers (both the module parameters and the in-code
address lists). I think it was a very good move, as the ranges can
easily be replaced by individual addresses, and this allowed for
significant cleanups in the i2c core (let alone the impressive size
shrink for all these drivers).

Unfortunately you did not do the same for non-sensors i2c chip drivers.
These need the address ranges even less, so we could get rid of the
ranges here as well for another significant i2c core cleanup. Here comes
a patch which does just that. Since the process is exactly the same as
what you did for the other drivers set already, I did not split this one
in parts.

A documentation update is included.

The change saves 308 bytes in the i2c core, and an average 1382 bytes
for chip drivers which use I2C_CLIENT_INSMOD, 126 bytes for those which
do not.

This change is required if we want to merge the sensors and non-sensors
i2c code (and we want to do this).
Signed-off-by: NJean Delvare <khali@linux-fr.org>
Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>

Index: gregkh-2.6/Documentation/i2c/writing-clients
===================================================================
      b3d5496e
  33. 07 5月, 2005 1 次提交