From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tty: the briq panel isn't a tty, make it use its own locking
Date: Fri, 24 Feb 2012 07:42:27 +1100 [thread overview]
Message-ID: <1330029747.20389.37.camel@pasglop> (raw)
In-Reply-To: <20120223133931.6227.89653.stgit@bob.linux.org.uk>
On Thu, 2012-02-23 at 13:39 +0000, Alan Cox wrote:
> From: Alan Cox <alan@linux.intel.com>
>
> The driver appears to be terminall broken, if nobody is maintaining it then
> perhaps it should go into staging and the out-tray.
Hrm, I don't think anybody maintains it but I do have a BriQ somewhere
in storage, so I suppose I could pick it up, not that I need another
crap driver to deal with right now though...
Cheers,
Ben.
> (Fixed bug noted by Jiri)
>
> Signed-off-by: Alan Cox <alan@linux.intel.com>
> ---
>
> drivers/char/briq_panel.c | 26 +++++++-------------------
> 1 files changed, 7 insertions(+), 19 deletions(-)
>
>
> diff --git a/drivers/char/briq_panel.c b/drivers/char/briq_panel.c
> index 095ab90..3335d07 100644
> --- a/drivers/char/briq_panel.c
> +++ b/drivers/char/briq_panel.c
> @@ -20,6 +20,7 @@
> #include <linux/mm.h>
> #include <linux/init.h>
>
> +#include <asm/bitops.h>
> #include <asm/uaccess.h>
> #include <asm/io.h>
> #include <asm/prom.h>
> @@ -30,7 +31,7 @@
> #define BRIQ_PANEL_VER "1.1 (04/20/2002)"
> #define BRIQ_PANEL_MSG0 "Loading Linux"
>
> -static int vfd_is_open;
> +static unsigned long vfd_is_open;
> static unsigned char vfd[40];
> static int vfd_cursor;
> static unsigned char ledpb, led;
> @@ -66,37 +67,27 @@ static void set_led(char state)
>
> static int briq_panel_open(struct inode *ino, struct file *filep)
> {
> - tty_lock();
> - /* enforce single access, vfd_is_open is protected by BKL */
> - if (vfd_is_open) {
> - tty_unlock();
> + /* enforce single open */
> + if (test_and_set_bit(0, &vfd_is_open))
> return -EBUSY;
> }
> - vfd_is_open = 1;
> -
> - tty_unlock();
> return 0;
> }
>
> static int briq_panel_release(struct inode *ino, struct file *filep)
> {
> - if (!vfd_is_open)
> - return -ENODEV;
> -
> - vfd_is_open = 0;
> -
> + clear_bit(0, &vfd_is_open);
> return 0;
> }
>
> +/* Note that single open doesn't mean single threaded read or write so all
> + this code is unsafe */
> static ssize_t briq_panel_read(struct file *file, char __user *buf, size_t count,
> loff_t *ppos)
> {
> unsigned short c;
> unsigned char cp;
>
> - if (!vfd_is_open)
> - return -ENODEV;
> -
> c = (inb(BRIQ_PANEL_LED_IOPORT) & 0x000c) | (ledpb & 0x0003);
> set_led(' ');
> /* upper button released */
> @@ -137,9 +128,6 @@ static ssize_t briq_panel_write(struct file *file, const char __user *buf, size_
> size_t indx = len;
> int i, esc = 0;
>
> - if (!vfd_is_open)
> - return -EBUSY;
> -
> for (;;) {
> char c;
> if (!indx)
next prev parent reply other threads:[~2012-02-23 20:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 13:39 [PATCH] tty: the briq panel isn't a tty, make it use its own locking Alan Cox
2012-02-23 20:42 ` Benjamin Herrenschmidt [this message]
2012-02-23 22:56 ` Alan Cox
2012-02-24 1:08 ` Josh Boyer
2012-02-24 1:37 ` Benjamin Herrenschmidt
2012-02-29 20:21 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2012-02-23 12:34 Alan Cox
2012-02-23 12:37 ` Jiri Slaby
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=1330029747.20389.37.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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).