linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Chris Metcalf <cmetcalf@tilera.com>
Cc: linux-kernel@vger.kernel.org,
	"Eric W. Biederman" <ebiederm@aristanetworks.com>,
	Chris Wright <chrisw@sous-sol.org>,
	"Greg Kroah-Hartman" <gregkh@suse.de>,
	Benjamin Thery <benjamin.thery@bull.net>,
	Phil Carmody <ext-phil.2.carmody@nokia.com>
Subject: Re: [PATCH] arch/tile: add arch/tile/drivers/ directory with SROM driver
Date: Fri, 20 May 2011 20:46:40 +0200	[thread overview]
Message-ID: <201105202046.40696.arnd@arndb.de> (raw)
In-Reply-To: <4DD6AD51.7090900@tilera.com>

On Friday 20 May 2011 20:05:05 Chris Metcalf wrote:
> This works well, except for the fact that we take advantage of the fact
> that the hypervisor driver internally buffers up writes to the current
> EEPROM sector, and flushes it to hardware only when explicitly told to do
> so, or when we start writing to another sector.  This avoids excessive wear
> on the EEPROM and also handles detection of whether we need to do a sector
> erase before the re-write.  However, it also means that we need to be able
> to issue the final explicit flush, or else the last write just sits in the
> hypervisor buffer indefinitely.  To make that happen I think I need to
> extend the bin_attribute structure, and the bin.c release() function, slightly:

Yes, that would work. Another option would be to add a flush() callback
to the bin_attribute. Since filp_close calls both fops->flush and
fops->release, that would also make it possible to flush the buffer
without closing it, if necessary.

	Arnd

  reply	other threads:[~2011-05-20 18:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-04 19:10 [PATCH] arch/tile: add arch/tile/drivers/ directory with SROM driver Chris Metcalf
2011-05-05  6:41 ` Arnd Bergmann
2011-05-06 19:37   ` Chris Metcalf
2011-05-20 18:05   ` Chris Metcalf
2011-05-20 18:46     ` Arnd Bergmann [this message]
2011-05-20 22:40       ` Eric Biederman
2011-05-20 23:39         ` Chris Metcalf
2011-05-21  3:21           ` Greg KH
2011-05-21  9:33             ` Arnd Bergmann
2011-05-21 13:52               ` Chris Metcalf
2011-05-21 15:02                 ` Arnd Bergmann
2011-05-21 15:31                   ` Chris Metcalf
2011-05-21 15:50                 ` Eric Biederman
2011-05-23 20:10                   ` Chris Metcalf
2011-05-21  7:46           ` Eric Biederman
2011-05-21  8:32             ` Arnd Bergmann
2011-05-22  0:54               ` Mike Frysinger
2011-05-28 15:13 ` [PATCH v2] arch/tile: add hypervisor-based character driver for SPI flash ROM Chris Metcalf
2011-05-28 21:23   ` Greg KH
2011-05-29  0:32     ` Chris Metcalf
2011-05-29 11:45       ` Greg KH
2011-05-29 12:18         ` Chris Metcalf
2011-05-29 13:47           ` Greg KH
2011-05-29 15:45           ` Arnd Bergmann
2011-05-29 18:23             ` Chris Metcalf
2011-06-02 15:04   ` [PATCH v3] " Chris Metcalf
2011-06-10 16:41     ` Arnd Bergmann

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=201105202046.40696.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=benjamin.thery@bull.net \
    --cc=chrisw@sous-sol.org \
    --cc=cmetcalf@tilera.com \
    --cc=ebiederm@aristanetworks.com \
    --cc=ext-phil.2.carmody@nokia.com \
    --cc=gregkh@suse.de \
    --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).