linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Adrian McMenamin <adrian@newgolddream.dyndns.info>
Cc: linux-kernel@vger.kernel.org, dmitry.torokhov@gmail.com,
	linux-sh@vger.kernel.org, lethal@linux-sh.org
Subject: Re: [PATCH] sh: maple: add support for Maple controller as a
Date: Mon, 22 Dec 2008 23:06:36 +0000	[thread overview]
Message-ID: <20081222150636.8dc20d61.akpm@linux-foundation.org> (raw)
In-Reply-To: <1229728542.1441.6.camel@localhost.localdomain>

On Fri, 19 Dec 2008 23:15:42 +0000
Adrian McMenamin <adrian@newgolddream.dyndns.info> wrote:

> Not sure what happened with earlier submissions, so here is an up-to-date
> patch for the Dreamcast Maple controlled.
> 
> 
> Add support for the SEGA Dreamcast Maple controller as a joystick
> 
> ...
>
> +static void dc_pad_callback(struct mapleq *mq)
> +{
> +	unsigned short buttons;
> +	struct maple_device *mapledev = mq->dev;
> +	struct dc_pad *pad = maple_get_drvdata(mapledev);
> +	struct input_dev *dev = pad->dev;
> +	unsigned char *res = mq->recvbuf;
> +
> +	buttons = ~cpu_to_le16(*(unsigned short *)(res + 8));

hm, could that be simplified?

> +	input_report_abs(dev, ABS_HAT0Y,
> +			 (buttons & 0x0010 ? -1:0) + (buttons & 0x0020 ? 1:0));
> +	input_report_abs(dev, ABS_HAT0X,
> +			 (buttons & 0x0040 ? -1:0) + (buttons & 0x0080 ? 1:0));
> +	input_report_abs(dev, ABS_HAT1Y,
> +			 (buttons & 0x1000 ? -1:0) + (buttons & 0x2000 ? 1:0));
> +	input_report_abs(dev, ABS_HAT1X,
> +			 (buttons & 0x4000 ? -1:0) + (buttons & 0x8000 ? 1:0));
> +
> +	input_report_key(dev, BTN_C,      buttons & 0x0001);
> +	input_report_key(dev, BTN_B,      buttons & 0x0002);
> +	input_report_key(dev, BTN_A,      buttons & 0x0004);
> +	input_report_key(dev, BTN_START,  buttons & 0x0008);
> +	input_report_key(dev, BTN_Z,      buttons & 0x0100);
> +	input_report_key(dev, BTN_Y,      buttons & 0x0200);
> +	input_report_key(dev, BTN_X,      buttons & 0x0400);
> +	input_report_key(dev, BTN_SELECT, buttons & 0x0800);
> +
> +	input_report_abs(dev, ABS_GAS,   res[10]);
> +	input_report_abs(dev, ABS_BRAKE, res[11]);
> +	input_report_abs(dev, ABS_X,     res[12]);
> +	input_report_abs(dev, ABS_Y,     res[13]);
> +	input_report_abs(dev, ABS_RX,    res[14]);
> +	input_report_abs(dev, ABS_RY,    res[15]);
> +}
> +
> +static int dc_pad_open(struct input_dev *dev)
> +{
> +	struct dc_pad *pad;
> +
> +	pad = dev->dev.platform_data;
> +	maple_getcond_callback(pad->mdev, dc_pad_callback, HZ/20,
> +		MAPLE_FUNC_CONTROLLER);
> +	return 0;
> +}
> +
> +static void dc_pad_close(struct input_dev *dev)
> +{
> +	struct dc_pad *pad;
> +	
> +	pad = dev->dev.platform_data;
> +	maple_getcond_callback(pad->mdev, dc_pad_callback, 0,
> +		MAPLE_FUNC_CONTROLLER);
> +}
> +
> +/* allow the controller to be used */
> +static int probe_maple_controller(struct device *dev)
> +{
> +	struct maple_device *mdev = to_maple_dev(dev);
> +	struct maple_driver *mdrv = to_maple_driver(dev->driver);
> +	int i, error;
> +	struct dc_pad *pad;
> +	struct input_dev *idev;
> +	unsigned long data = be32_to_cpu(mdev->devinfo.function_data[0]);
> +
> +	const short btn_bit[32] = {
> +		BTN_C, BTN_B, BTN_A, BTN_START, -1, -1, -1, -1,
> +		BTN_Z, BTN_Y, BTN_X, BTN_SELECT, -1, -1, -1, -1,
> +		-1, -1, -1, -1, -1, -1, -1, -1,
> +		-1, -1, -1, -1, -1, -1, -1, -1,
> +	};
> +
> +	const short abs_bit[32] = {
> +		-1, -1, -1, -1, ABS_HAT0Y, ABS_HAT0Y, ABS_HAT0X, ABS_HAT0X,
> +		-1, -1, -1, -1, ABS_HAT1Y, ABS_HAT1Y, ABS_HAT1X, ABS_HAT1X,
> +		ABS_GAS, ABS_BRAKE, ABS_X, ABS_Y, ABS_RX, ABS_RY, -1, -1,
> +		-1, -1, -1, -1, -1, -1, -1, -1,
> +	};

These could be made static.

There's a risk that the compiler will go and assemble these arrays on
the stack each time this function is called.  gcc (some versions, at
least) will actually internally turn these into static arrays
(assembled at compile time) but it's best to do this explicitly.


> +	pad = kzalloc(sizeof(struct dc_pad), GFP_KERNEL);
> +	idev = input_allocate_device();
> +	if (!pad || !idev){
> +		error = ENOMEM;
>
> ...
>
> +	return -error;

Please don't do this.  People occasionally grep the tree for instances
of 'EFOO' which are missing the "-" sign, which is a useful service. 
The above trick just makes things harder for them.

>
> ...
>

  parent reply	other threads:[~2008-12-22 23:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-19 23:15 [PATCH] sh: maple: add support for Maple controller as a joystick Adrian McMenamin
2008-12-20 15:16 ` [PATCH] sh: maple: add support for Maple controller as a Matt Fleming
2008-12-20 16:07   ` Adrian McMenamin
2008-12-20 20:19     ` [PATCH] sh: maple: add support for Maple controller as a joystick Dmitry Torokhov
2008-12-20 20:47       ` [PATCH] sh: maple: add support for Maple controller as a Adrian McMenamin
2008-12-20 22:17         ` [PATCH] sh: maple: add support for Maple controller as a joystick Dmitry Torokhov
2008-12-21  6:47 ` Paul Mundt
2008-12-21  9:28 ` [PATCH] sh: maple: add support for Maple controller as a Rabin Vincent
2008-12-22 23:06 ` Andrew Morton [this message]
2008-12-23  1:07   ` Harvey Harrison
2008-12-23  8:59     ` Dmitry Torokhov
2008-12-26 19:08       ` Adrian McMenamin

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=20081222150636.8dc20d61.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=adrian@newgolddream.dyndns.info \
    --cc=dmitry.torokhov@gmail.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).