linux-kernel - Re: [PATCH] PalmTX initial support

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]

Message-ID: <20080702220356.GE19143@flint.arm.linux.org.uk>
Date:	Wed, 2 Jul 2008 23:03:56 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Ben Dooks <ben-linux@...ff.org>,
	Marek Va??ut <marek.vasut@...il.com>
Cc:	linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.arm.linux.org.uk
Subject: Re: [PATCH] PalmTX initial support

On Wed, Jul 02, 2008 at 09:41:10PM +0100, Ben Dooks wrote:
> hmm, why isn't the pxa sdmmc driver doing something about the
> detection for the cards?

Because there's no standard way to detect MMC cards on PXA hardware.

> > +/******************************************************************************
> > + * GPIO keys
> > + ******************************************************************************/
> > +#ifdef CONFIG_KEYBOARD_GPIO
> > +static struct gpio_keys_button palmtx_pxa_buttons[] = {
> > +	{KEY_F8, GPIO_NR_PALMTX_HOTSYNC_BUTTON_N, 1, "HotSync Button" },
> > +};
> 
> I've never seen the pooint of #ifdefs for platform data, just bung
> the lot in, it is always possible to build and an insert a new driver
> module to support this after building the zImage.

And this initialiser should be using named initialisers.

> > +static struct generic_bl_info palmtx_bl_info = {
> > +	.max_intensity		= PALMTX_MAX_INTENSITY,
> > +	.default_intensity	= PALMTX_MAX_INTENSITY,
> > +	.set_bl_intensity	= palmtx_set_bl_intensity,
> > +	.limit_mask		= PALMTX_LIMIT_MASK,
> > +};
> 
> go and have a look at the new pwm stuff.

It's found in the 'pxa' branch of my git tree.  See the website for a link
to it.

> > +static void palmtx_irda_transceiver_mode(struct device *dev, int mode)
> > +{
> > +	unsigned long flags;
> > +
> > +	local_irq_save(flags);
> > +
> > +	if (mode & IR_SIRMODE)
> > +		printk(KERN_INFO "IrDA: setting mode to SIR\n");
> > +	else if (mode & IR_FIRMODE)
> > +		printk(KERN_INFO "IrDA: setting mode to FIR\n");

Are these useful?

> > +
> > +	if (mode & IR_OFF) {
> > +		printk(KERN_INFO "IrDA: turning transceiver OFF\n");

Ditto.

> > +		gpio_set_value(GPIO_NR_PALMTX_IR_DISABLE, 1);
> > +	} else {
> > +		printk(KERN_INFO "IrDA: turning transceiver ON\n");

Ditto.

> > +		gpio_set_value(GPIO_NR_PALMTX_IR_DISABLE, 0);
> > +		gpio_set_value(GPIO47_ICPTXD_MD, 1);
> > +		mdelay(30);
> > +		gpio_set_value(GPIO47_ICPTXD_MD, 0);

Don't you have to configure GPIO47 as a GPIO to change its state?
Since you don't, and I assume you've tested this, I think you've
proven that you can delete the fiddling with GPIO47.

> > +/******************************************************************************
> > + * AC97
> > + ******************************************************************************/
> > +static struct platform_device palmtx_ac97 = {
> > +	.name	= "pxa2xx-ac97",
> > +	.id	= 0,
> > +};

There's an AC97 device now in the pxa branch.
--
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/