public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rodolfo Giometti <giometti@enneenne.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Add c2 port support.
Date: Wed, 22 Oct 2008 21:52:46 +0200	[thread overview]
Message-ID: <20081022195245.GS4390@tekkaman> (raw)
In-Reply-To: <20081022111145.e5f3c632.akpm@linux-foundation.org>

On Wed, Oct 22, 2008 at 11:11:45AM -0700, Andrew Morton wrote:

> No opinion yet - I haven't review them.
> 
> <looks>
> 
> <wonders why c2port_idr_lock and c2port_idr are kernel-wide symbols>

Fixed.

> <wonders what local_irq_disable() is supposed to achieve on SMP>

The SMP is achieved by mutex_lock(), the local_irq_disable() is used
to avoid interructions in code execution. C2 port has very stringent
timings.

> <spots an error-path memory leak in c2port_device_register>
> 
> <spots a stray semicolon in c2port_device_register>

Can you please explain these two points?

> <suggests that update_lock be initialised at compile-time, not at runtime>

Fixed.

> 
> What I haven't yet got my head around is this:
> 
>   Currently this code supports only flash programming through sysfs
>   interface but extensions shoud be easy to add.
> 
> is that really what we want to use sysfs for?  As the prime interface
> to a device driver (or is it a bus driver?) Didn't we used to use
> device nodes for that sort of thing?

I decided to use this interface since the C2 ports are simple and very
easy to manage with such files abstraction.

Whould you like I repropose the code with the fixed issues for your
review?

Thanks for your suggestions,

Rodolfo

-- 

GNU/Linux Solutions                  e-mail: giometti@enneenne.com
Linux Device Driver                          giometti@linux.it
Embedded Systems                     phone:  +39 349 2432127
UNIX programming                     skype:  rodolfo.giometti

  reply	other threads:[~2008-10-22 19:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-22 13:47 c2port (Version 2): support for Silicon C2 Interface Rodolfo Giometti
2008-10-22 13:47 ` [PATCH 1/2] Add c2 port support Rodolfo Giometti
2008-10-22 13:47   ` [PATCH 2/2] c2port: add c2port support for Eurotech Duramar 2150 Rodolfo Giometti
2008-10-22 17:40     ` Greg KH
2008-10-22 17:40   ` [PATCH 1/2] Add c2 port support Greg KH
2008-10-22 18:11     ` Andrew Morton
2008-10-22 19:52       ` Rodolfo Giometti [this message]
2008-10-22 20:01         ` Andrew Morton
2008-10-22 20:48           ` Rodolfo Giometti
2008-10-22 20:58             ` Andrew Morton
2008-10-22 21:03               ` Greg KH
2008-10-23  7:39                 ` Rodolfo Giometti
2008-10-23 15:37                   ` Greg KH
2008-10-27  8:54                     ` Rodolfo Giometti
2008-10-27 16:14                       ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2008-10-22 20:53 c2port (Version 3): support for Silicon C2 Interface Rodolfo Giometti
2008-10-22 20:53 ` [PATCH 1/2] Add c2 port support Rodolfo Giometti

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=20081022195245.GS4390@tekkaman \
    --to=giometti@enneenne.com \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --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