linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Enric Balletbo Serra <eballetbo@gmail.com>
To: Moritz Fischer <mdf@kernel.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Enric Balletbo i Serra <enric.balletbo@collabora.com>,
	Benson Leung <bleung@chromium.org>,
	Guenter Roeck <groeck@chromium.org>,
	Lee Jones <lee.jones@linaro.org>,
	Moritz Fischer <moritz@ettus.com>
Subject: Re: [PATCH v3] platform/chrome: Add cros_ec_readmem() helpers for I2C/SPI based ECs
Date: Mon, 21 Jan 2019 23:19:34 +0100	[thread overview]
Message-ID: <CAFqH_50fsPx1raFReNt719fT2DmgAb0YHwzzbmfdAy9gYigLiA@mail.gmail.com> (raw)
In-Reply-To: <20190121184017.GA5761@archbook>

Hi Moritz,

Missatge de Moritz Fischer <mdf@kernel.org> del dia dl., 21 de gen.
2019 a les 19:40:
>
> Hi Enrico,
>
> On Mon, Jan 21, 2019 at 06:32:48PM +0100, Enric Balletbo Serra wrote:
> > Hi Moritz,
> >
> > Missatge de Moritz Fischer <mdf@kernel.org> del dia dj., 10 de gen.
> > 2019 a les 5:40:
> > >
> > > Add cros_ec_readmem() helpers for I2C/SPI based ECs.
> > > Unlike the LPC based ECs the I2C/SPI based ones cannot just directly
> > > read the mapped region, but have to resort to EC_CMD_READ_MEMMAP.
> > >
> > > This is useful for things like accessing fan speeds or temperatures.
> > >
> > > Signed-off-by: Moritz Fischer <mdf@kernel.org>
> > > ---
> > >
> > > Hi all,
> > >
> > > This can be used for a hwmon or thermal driver such as [1], but also
> > > alone can be used with 'ectool' via the ioctl() interface.
> > >
> >
> > ooi, did you try this with a Chromebook? Or only with your device?
>
> Nope, mine has a dead battery (and no fans ... :-/)
> >
> > I was a bit worried on the side effects to expose this command to
> > userspace, so I did a quick test, and to be honest I didn't like the
> > result. Issuing the ioctl resulted on a reboot on the Chromebook I
> > tested, which is not good. I didn't investigate more but I can say
> > that this change, at least, will need some rework. I'll try to
> > investigate a bit more on what is happening.
>
> That sounds bad :-/
>
> What chromebook did you run this on (so I can look at the EC code it is
> running and figure out what's the difference). Maybe it has a different
> configuration. It wasn't an x86 chromebook, right?
>

I tried with a Samsung Chromebook Plus (arm64 Chromebook)

> What was the ioctl you ran?
>

The code that I ran is this: https://hastebin.com/cupecuvowi.py
No guarantee :) I'll try to look deeper tomorrow.

Thanks,
  Enric

> Thanks for testing,
> Moritz

  reply	other threads:[~2019-01-21 22:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-10  4:36 [PATCH v3] platform/chrome: Add cros_ec_readmem() helpers for I2C/SPI based ECs Moritz Fischer
2019-01-21 17:32 ` Enric Balletbo Serra
2019-01-21 18:40   ` Moritz Fischer
2019-01-21 22:19     ` Enric Balletbo Serra [this message]
2019-01-22 21:09       ` Moritz Fischer
2019-01-23 11:33         ` Enric Balletbo Serra

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=CAFqH_50fsPx1raFReNt719fT2DmgAb0YHwzzbmfdAy9gYigLiA@mail.gmail.com \
    --to=eballetbo@gmail.com \
    --cc=bleung@chromium.org \
    --cc=enric.balletbo@collabora.com \
    --cc=groeck@chromium.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdf@kernel.org \
    --cc=moritz@ettus.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;
as well as URLs for NNTP newsgroup(s).