All of lore.kernel.org
 help / color / mirror / Atom feed
From: mchehab@brturbo.com.br (Mauro Carvalho Chehab)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] [PATCH] i2c: driver IDs cleanups
Date: Thu, 08 Dec 2005 20:46:22 +0000	[thread overview]
Message-ID: <1134074782.7047.146.camel@localhost> (raw)
In-Reply-To: <20051205220053.2571761d.khali@linux-fr.org>

Em Seg, 2005-12-05 ?s 22:00 +0100, Jean Delvare escreveu:
> Hi all,
> 
> As proposed recently in another thread, I am enqueuing the following
> patch:
> 
> Content-Disposition: inline; filename=i2c-id-cleanups.patch
> 
> Cleanups to i2c driver IDs:
> * Remove mostly bogus comments on driver ID ranges.
> * Drop experimental driver IDs, as the concept is pretty broken.
> * Drop now unused IDs of non-I2C (ISA) drivers.
> * Drop a few more IDs which are no more used.
> 
> Signed-off-by: Jean Delvare <khali at linux-fr.org>
Acked-off-by: Mauro Carvalho Chehab
> ---
>  include/linux/i2c-id.h |   20 --------------------
>  1 file changed, 20 deletions(-)
> 
> --- linux-2.6.15-rc5.orig/include/linux/i2c-id.h	2005-12-04 09:54:04.000000000 +0100
> +++ linux-2.6.15-rc5/include/linux/i2c-id.h	2005-12-05 21:04:49.000000000 +0100
> @@ -25,12 +25,6 @@
>  
>  /*
>   * ---- Driver types -----------------------------------------------------
> - *       device id name + number        function description, i2c address(es)
> - *
> - *  Range 1000-1999 range is defined in sensors/sensors.h
> - *  Range 0x100 - 0x1ff is for V4L2 Common Components
> - *  Range 0xf000 - 0xffff is reserved for local experimentation, and should
> - *        never be used in official drivers
>   */
>  
>  #define I2C_DRIVERID_MSP3400	 1
> @@ -110,13 +104,7 @@
>  #define I2C_DRIVERID_AKITAIOEXP	74	/* IO Expander on Sharp SL-C1000 */
>  #define I2C_DRIVERID_I2C_IR	75	/* I2C InfraRed on Video boards */
>  
> -#define I2C_DRIVERID_EXP0	0xF0	/* experimental use id's	*/
> -#define I2C_DRIVERID_EXP1	0xF1
> -#define I2C_DRIVERID_EXP2	0xF2
> -#define I2C_DRIVERID_EXP3	0xF3
> -
>  #define I2C_DRIVERID_I2CDEV	900
> -#define I2C_DRIVERID_I2CPROC	901
>  #define I2C_DRIVERID_ARP        902    /* SMBus ARP Client              */
>  #define I2C_DRIVERID_ALERT      903    /* SMBus Alert Responder Client  */
>  
> @@ -131,15 +119,12 @@
>  #define I2C_DRIVERID_ADM1021 1008
>  #define I2C_DRIVERID_ADM9240 1009
>  #define I2C_DRIVERID_LTC1710 1010
> -#define I2C_DRIVERID_SIS5595 1011
>  #define I2C_DRIVERID_ICSPLL 1012
>  #define I2C_DRIVERID_BT869 1013
>  #define I2C_DRIVERID_MAXILIFE 1014
>  #define I2C_DRIVERID_MATORB 1015
>  #define I2C_DRIVERID_GL520 1016
>  #define I2C_DRIVERID_THMC50 1017
> -#define I2C_DRIVERID_DDCMON 1018
> -#define I2C_DRIVERID_VIA686A 1019
>  #define I2C_DRIVERID_ADM1025 1020
>  #define I2C_DRIVERID_LM87 1021
>  #define I2C_DRIVERID_PCF8574 1022
> @@ -151,21 +136,16 @@
>  #define I2C_DRIVERID_FSCPOS 1028
>  #define I2C_DRIVERID_FSCSCY 1029
>  #define I2C_DRIVERID_PCF8591 1030
> -#define I2C_DRIVERID_SMSC47M1 1031
> -#define I2C_DRIVERID_VT1211 1032
>  #define I2C_DRIVERID_LM92 1033
> -#define I2C_DRIVERID_VT8231 1034
>  #define I2C_DRIVERID_SMARTBATT 1035
>  #define I2C_DRIVERID_BMCSENSORS 1036
>  #define I2C_DRIVERID_FS451 1037
> -#define I2C_DRIVERID_W83627HF 1038
>  #define I2C_DRIVERID_LM85 1039
>  #define I2C_DRIVERID_LM83 1040
>  #define I2C_DRIVERID_LM90 1042
>  #define I2C_DRIVERID_ASB100 1043
>  #define I2C_DRIVERID_FSCHER 1046
>  #define I2C_DRIVERID_W83L785TS 1047
> -#define I2C_DRIVERID_SMSC47B397 1050
>  
>  /*
>   * ---- Adapter types ----------------------------------------------------
> 
> 
Cheers, 
Mauro.



      reply	other threads:[~2005-12-08 20:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-05 21:00 [lm-sensors] [PATCH] i2c: driver IDs cleanups Jean Delvare
2005-12-08 20:46 ` Mauro Carvalho Chehab [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=1134074782.7047.146.camel@localhost \
    --to=mchehab@brturbo.com.br \
    --cc=lm-sensors@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.