linux-kernel - Re: [PATCH v2] lis3: Add support for new LIS3DC / HP3DC chip

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 23 Sep 2010 22:08:12 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Samu Onkalo <samu.p.onkalo@...ia.com>,
	Éric Piel <Eric.Piel@...mplin-utc.net>,
	Guenter Roeck <guenter.roeck@...csson.com>,
	linux-kernel@...r.kernel.org, lm-sensors@...sensors.org
Subject: Re: [PATCH v2] lis3: Add support for new LIS3DC / HP3DC chip

At Thu, 23 Sep 2010 12:43:13 -0700,
Andrew Morton wrote:
> 
> On Thu, 23 Sep 2010 08:01:31 +0200
> Takashi Iwai <tiwai@...e.de> wrote:
> 
> > A new version of LIS3 chip has slight incompatibilities from former
> > versions.  This patch adds the minimal support for it.
> > 
> > Signed-off-by: Takashi Iwai <tiwai@...e.de>
> > ---
> > v1->v2
> >   Rebased to patch "lis3: Fix Oops with NULL platform data (v2)"
> > 
> 
> Wait.  I did my own rebasing and came up with a different patch, with
> two extra hunks:
> 
> @@ -301,8 +311,9 @@ static irqreturn_t lis302dl_interrupt(in
>  	wake_up_interruptible(&lis3_dev.misc_wait);
>  	kill_fasync(&lis3_dev.async_queue, SIGIO, POLL_IN);
>  out:
> -	if (lis3_dev.pdata && lis3_dev.whoami == WAI_8B && lis3_dev.idev &&
> -	    lis3_dev.idev->input->users)
> +	if (lis3_dev.pdata &&
> +		(lis3_dev.whoami == WAI_8B || lis3_dev.whoami == WAI_3DC) &&
> +		lis3_dev.idev && lis3_dev.idev->input->users)
>  		return IRQ_WAKE_THREAD;
>  	return IRQ_HANDLED;
>  }
> 
> and
> 
> @@ -742,7 +762,7 @@ int lis3lv02d_init_device(struct lis3lv0
>  	 * io-apic is not configurable (and generates a warning) but I keep it
>  	 * in case of support for other hardware.
>  	 */
> -	if (dev->pdata && dev->whoami == WAI_8B)
> +	if (dev->pdata && (dev->whoami == WAI_8B || dev->whoami == WAI_3DC))
>  		thread_fn = lis302dl_interrupt_thread1_8b;
>  	else
>  		thread_fn = NULL;
> 
> 
> Did you drop those changes deliberately?

IMO, safer to drop these, so far.
For platform-specific, the driver requires the initialization of some
registers, and currently it's only for WAI_8B chips.  WAI_3DC has
incompatibilities and cannot use it as is.


thanks,

Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/