mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Paul Sokolovsky" <pmiscml@gmail.com>
Cc: "Greg KH" <gregkh@suse.de>,
	"Arjan van de Ven" <arjan@infradead.org>,
	"Jiri Slaby" <jirislaby@gmail.com>,
	linux-kernel@vger.kernel.org, "Adrian Bunk" <bunk@stusta.de>,
	kernel-discuss@handhelds.org
Subject: Re: Re[2]: Where did find_bus() go in 2.6.18?
Date: Tue, 21 Nov 2006 14:02:26 -0500	[thread overview]
Message-ID: <d120d5000611211102w79d6729cx75f04c731ccc943c@mail.gmail.com> (raw)
In-Reply-To: <1148526308.20061120161322@gmail.com>

On 11/20/06, Paul Sokolovsky <pmiscml@gmail.com> wrote:
>
> [Uninteresting specific case]
>
>  Ok, so the situation is following: we have a kind of multi-layered
> driver here. Lowest level is a w1_slave bus driver, talking to a
> specific chip and providing low-level API for accessing data in terms
> of this chip (or chip class) notions. Above it, we have higher-level
> driver which interprets data from the low-level one, converting it to
> a standard device-independent form, plus possibly does some other
> minor things, like providing feedback indication on these data.
> (Forgot to say that this is battery driver.)
>
>  So, just in case if some reader of this has quick suggestion of
> merging these drivers into one, thanks, but they do different things,
> and we want to keep them nicely decoupled. But now issue of how these
> drivers talk between themselves raises, and that's exactly the grief
> point.
>

My suggestion would be do define a class for your device independent
data and have low-level driver create a class device (or just a device
if Greg has his way with driver core) and change your high-level
driver to become a class interface.

And then you won't have to rescan w1 bus every 5 seconds for that battery...

-- 
Dmitry

  parent reply	other threads:[~2006-11-21 19:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-19 22:34 Paul Sokolovsky
2006-11-19 23:45 ` Jiri Slaby
2006-11-20  0:12   ` Greg KH
2006-11-20 14:13     ` Re[2]: " Paul Sokolovsky
2006-11-20 17:35       ` Adrian Bunk
2006-11-21 15:08         ` Re[2]: " Paul Sokolovsky
2006-11-21 15:16           ` Arjan van de Ven
2006-11-21 18:04           ` Adrian Bunk
2006-11-21  7:54       ` Greg KH
2006-11-22  8:36         ` Re[2]: " Paul Sokolovsky
2006-11-21 19:02       ` Dmitry Torokhov [this message]
2006-11-20  0:13   ` Paul Sokolovsky
2006-11-20  8:34     ` Arjan van de Ven
2006-11-21 18:29       ` Matthew Frost
2006-11-21 19:01         ` Evgeniy Polyakov
2006-11-21 19:41           ` Re[2]: " Paul Sokolovsky
2006-11-21 20:34             ` Matthew Frost
2006-11-20  9:35 ` pHilipp Zabel

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=d120d5000611211102w79d6729cx75f04c731ccc943c@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=arjan@infradead.org \
    --cc=bunk@stusta.de \
    --cc=gregkh@suse.de \
    --cc=jirislaby@gmail.com \
    --cc=kernel-discuss@handhelds.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmiscml@gmail.com \
    /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

all inboxes | Powered by JetHome®