linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	linux-input@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH 1/1] Input: add sensable phantom driver
Date: Wed, 7 Mar 2007 09:47:08 -0500	[thread overview]
Message-ID: <d120d5000703070647t223f8858i8c495dcc3e1378a2@mail.gmail.com> (raw)
In-Reply-To: <2460126662758025813@fi.muni.cz>

Hi Jiri,

On 3/7/07, Jiri Slaby <jirislaby@gmail.com> wrote:
> add sensable phantom driver
...

General question - can this driver use force-feedback mecahnisms
already present in kernel instead of exporting raw datastream to
userspace. What are shortcomings of kernels force-feedback
implemenattion that make it insufficient for phantom?

> +
> +#define phantom_remap(io, vma, addr)   ({                              \
> +       vma->vm_pgoff = (addr) >> PAGE_SHIFT;                           \
> +       io ## remap_pfn_range(vma, (vma)->vm_start, (vma)->vm_pgoff,    \
> +               (vma)->vm_end - (vma)->vm_start, (vma)->vm_page_prot);  \
> +})
> +
> +static int phantom_mmap(struct file *file, struct vm_area_struct *vma)
> +{
> +       struct phantom_device *dev = file->private_data;
> +       int retval;
> +
> +       switch (vma->vm_pgoff) {
> +       case 0:
> +               retval = phantom_remap(, vma, virt_to_phys(dev->stat));

This really hurts my eyes. Is there any reason for using the macro here?
> +               break;
> +       case 1:
> +               retval = phantom_remap(io_, vma, dev->ibase);
> +               break;
> +       default:
> +               retval = phantom_remap(io_, vma, dev->obase);
> +       }
> +
> +       return retval ? -EINVAL : 0;
> +}
> +
> +
> +static int __devinit phantom_probe(struct pci_dev *pdev,
> +       const struct pci_device_id *pci_id)
> +{
> +       struct phantom_device *pht;
> +       unsigned int minor;
> +       int retval;
> +
> +       retval = pci_enable_device(pdev);
> +       if (retval)
> +               goto err;
> +
> +       minor = phantom_get_free();
> +       if (minor == PHANTOM_MAX_MINORS) {
> +               dev_err(&pdev->dev, "too many devices found!\n");
> +               retval = -EIO;
> +               goto err;
> +       }
> +
> +       phantom_devices[minor] = 1;

Locking? In face of multithreaded PCI probes it might be needed.

> +
> +       retval = pci_request_regions(pdev, "phantom");
> +       if (retval)
> +               goto err_null;
> +
> +       retval = -ENOMEM;
> +       pht = kzalloc(sizeof(*pht), GFP_KERNEL);
> +       if (pht == NULL) {
> +               dev_err(&pdev->dev, "unable to allocate device\n");
> +               goto err_reg;
> +       }
> +
> +       pht->stat = (void *)__get_free_page(GFP_KERNEL | __GFP_WAIT);
> +       if (pht->stat == NULL)
> +               goto err_fr;
> +
> +       pht->caddr = pci_iomap(pdev, 0, 0);
> +       if (pht->caddr == NULL) {
> +               dev_err(&pdev->dev, "can't remap conf space\n");
> +               goto err_frp;
> +       }
> +       pht->ibase = pci_resource_start(pdev, 2);
> +       pht->obase = pci_resource_start(pdev, 3);
> +
> +       mutex_init(&pht->open_lock);
> +       init_waitqueue_head(&pht->wait);
> +
> +       phantom_write_cfgl(pht, 0, PHN_IRQCTL);
> +       retval = request_irq(pdev->irq, phantom_isr,
> +                       IRQF_SHARED | IRQF_DISABLED, "phantom", pht);
> +       if (retval) {
> +               dev_err(&pdev->dev, "can't establish ISR\n");
> +               goto err_unm;
> +       }
> +
> +       cdev_init(&pht->cdev, &phantom_file_ops);
> +       pht->cdev.owner = THIS_MODULE;
> +       retval = cdev_add(&pht->cdev, MKDEV(phantom_major, minor), 1);
> +       if (retval) {
> +               dev_err(&pdev->dev, "chardev registration failed\n");
> +               goto err_irq;
> +       }
> +
> +       device_create(phantom_class, &pdev->dev, MKDEV(phantom_major, minor),
> +                       "phantom%u", minor);
> +

Error handling is needed.

-- 
Dmitry

  reply	other threads:[~2007-03-07 14:47 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-07 11:36 [PATCH 1/1] Input: add sensable phantom driver Jiri Slaby
2007-03-07 14:47 ` Dmitry Torokhov [this message]
2007-03-07 16:38   ` Jiri Slaby
2007-03-07 16:50     ` Greg KH
2007-03-07 16:56     ` Dmitry Torokhov
2007-03-13 16:19       ` Jiri Slaby
     [not found]         ` <38b3b7c0703131450v2646e63fj2be4b9dda7f928c0@mail.gmail.com>
2007-03-13 22:16           ` FF layer restrictions [Was: [PATCH 1/1] Input: add sensable phantom driver] Jiri Slaby
2007-03-14 15:02             ` Dmitry Torokhov
2007-03-14 16:43               ` Jiri Slaby
2007-03-14 16:45                 ` Jiri Slaby
2007-03-14 18:04                 ` Anssi Hannula
2007-03-14 18:15                   ` Jiri Slaby
2007-03-14 18:47                   ` STenyaK (Bruno González)
2007-03-14 19:12                     ` STenyaK (Bruno González)
2007-03-14 19:13                     ` Dmitry Torokhov
2007-03-14 19:18                       ` STenyaK (Bruno González)
2007-03-15 20:51                         ` johann deneux
2007-03-15 21:06                           ` STenyaK (Bruno González)
2007-03-21 13:31                         ` Jiri Slaby
2007-03-21 13:32                           ` Jiri Slaby
2007-03-21 19:02                           ` johann deneux
2007-03-21 19:22                             ` Dmitry Torokhov
2007-03-21 20:04                               ` Jiri Slaby
2007-03-21 22:03                                 ` johann deneux
2007-03-22 15:50                                   ` Dmitry Torokhov
2007-03-27 12:20                                     ` Jiri Slaby
2007-03-27 18:36                                       ` johann deneux
2007-03-27 20:11                                         ` Jiri Slaby
2007-03-27 20:43                                           ` johann deneux
2007-03-27 20:51                                             ` Jiri Slaby
2007-03-27 21:34                                               ` johann deneux
2007-03-28  3:08                                                 ` Dmitry Torokhov
2007-03-28  9:28                                                   ` Jiri Slaby
2007-03-28 22:16                                                   ` Jiri Slaby
2007-03-28 22:22                                                     ` Jiri Slaby
2007-03-30 16:46                                                       ` Dmitry Torokhov
2007-03-30 19:11                                                 ` Anssi Hannula
2007-03-15 20:43                       ` johann deneux
2007-03-16 16:28               ` Pavel Machek
2007-03-17  7:28                 ` johann deneux

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=d120d5000703070647t223f8858i8c495dcc3e1378a2@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=jirislaby@gmail.com \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --cc=linux-kernel@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).