public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bruno Ducrot <ducrot@poupinou.org>
To: Johan Vromans <jvromans@squirrel.nl>
Cc: Rich Townsend <rhdt@bartol.udel.edu>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: RFC [PATCH] acpi: allow SMBus access
Date: Tue, 4 Jul 2006 11:35:10 +0200	[thread overview]
Message-ID: <20060704093510.GG17014@poupinou.org> (raw)
In-Reply-To: <m2d5cln659.fsf@phoenix.squirrel.nl>

On Tue, Jul 04, 2006 at 10:09:06AM +0200, Johan Vromans wrote:
> Bruno Ducrot <ducrot@poupinou.org> writes:
> 
> > I wanted to provide a real bus access via the EC driver, including
> > the interrupt driven ones.
> 
> Yes, that would be the right way to go. But it is a longer term
> solution and AFAIK noone is currently working on it.

Indeed

> In the mean time, several users can benefit from an intermediate
> solution like the one I suggested. Besides, it is not a wrong solution
> per se, it is equally wrong as the ac_read/write routines that are
> exported.

Yes, but I always considered the ec_read/write functions being an hack
in order to support sonypi at first.  If it's possible to kill them
and to replace them with the acpi_ec_read|write, well this would be
good IMHO.

> So I still think that exporting the current acpi_ec_read/write would
> be a good thing to so, but I agree it should be marked as an
> intermediate solution.

An intermediate solution would be to use the already existing
ec_read|write instead of the one you want to use.  The original
SMBus driver used acpi_ec_read because the author wanted to be
sure that driver will support laptops with more than one EC, but
he never saw such laptops so far.

Cheers,

-- 
Bruno Ducrot

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.

  reply	other threads:[~2006-07-04  9:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-02 21:12 RFC [PATCH] acpi: allow SMBus access Johan Vromans
2006-07-03  1:51 ` Yu Luming
2006-07-03  8:22   ` Bruno Ducrot
2006-07-03  8:22 ` Bruno Ducrot
2006-07-03 11:14   ` Johan Vromans
2006-07-03 12:51     ` Bruno Ducrot
2006-07-04  8:09       ` Johan Vromans
2006-07-04  9:35         ` Bruno Ducrot [this message]
2006-07-04 11:44           ` Johan Vromans
2006-07-06 13:58             ` Johan Vromans

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=20060704093510.GG17014@poupinou.org \
    --to=ducrot@poupinou.org \
    --cc=jvromans@squirrel.nl \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rhdt@bartol.udel.edu \
    /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