From: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
To: Olof Johansson <olof@lixom.net>, Gwendal Grignou <gwendal@chromium.org>
Cc: Lee Jones <lee.jones@linaro.org>,
Doug Anderson <dianders@chromium.org>,
Bill Richardson <wfrichar@chromium.org>,
Simon Glass <sjg@google.com>, Jonathan Corbet <corbet@lwn.net>,
Varka Bhadram <varkabhadram@gmail.com>,
Paul Bolle <pebolle@tiscali.nl>,
linux-samsung-soc@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 4/7] platform/chrome: Add Chrome OS EC userspace device interface
Date: Thu, 26 Feb 2015 10:08:31 +0100 [thread overview]
Message-ID: <54EEE28F.8000307@collabora.co.uk> (raw)
In-Reply-To: <CAMHSBOXOLrvkhWgF=hF8tB+yeakVUbTkTi-8ZvC2aAFtMEw_1A@mail.gmail.com>
Hello Olof,
Thanks a lot for your feedback.
On 02/26/2015 02:13 AM, Gwendal Grignou wrote:
> Olof,
>
> I think the way Javier did it is fine, the 'major' of the ioctl is
> 0xEC, from ':'.
>
> Gwendal.
>
As Gwendal said, I deliberately changed the IOCTL mayor number to
make it different in both kernels.
downstream:
#define CROS_EC_DEV_IOC ':'
#define CROS_EC_DEV_IOCXCMD _IOWR(':', 0, struct cros_ec_command)
#define CROS_EC_DEV_IOCRDMEM _IOWR(':', 1, struct cros_ec_readmem)
mainline:
#define CROS_EC_DEV_IOC 0xEC
#define CROS_EC_DEV_IOCXCMD _IOWR(CROS_EC_DEV_IOC, 0, struct cros_ec_command)
#define CROS_EC_DEV_IOCRDMEM _IOWR(CROS_EC_DEV_IOC, 1, struct cros_ec_readmem)
I can also do what you suggested and keep ':' as the major and use 2/3
as command numbers but I just think 0xEC is a much nicer major for the
interface to talk with the Embedded Controller and it was available ;)
Best regards,
Javier
next prev parent reply other threads:[~2015-02-26 9:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 11:26 [PATCH v5 0/7] platform/chrome: Add user-space dev inferface support Javier Martinez Canillas
2015-02-02 11:26 ` [PATCH v5 1/7] mfd: cros_ec: Use fixed size arrays to transfer data with the EC Javier Martinez Canillas
2015-02-02 11:26 ` [PATCH v5 2/7] mfd: cros_ec: Add char dev and virtual dev pointers Javier Martinez Canillas
2015-02-02 11:26 ` [PATCH v5 3/7] platform/chrome: Add cros_ec_lpc driver for x86 devices Javier Martinez Canillas
2015-02-02 11:26 ` [PATCH v5 4/7] platform/chrome: Add Chrome OS EC userspace device interface Javier Martinez Canillas
2015-02-26 0:54 ` Olof Johansson
2015-02-26 1:13 ` Gwendal Grignou
2015-02-26 9:08 ` Javier Martinez Canillas [this message]
2015-02-26 17:38 ` Olof Johansson
2015-02-02 11:26 ` [PATCH v5 5/7] mfd: cros_ec: Instantiate ChromeOS EC character device Javier Martinez Canillas
2015-02-02 11:26 ` [PATCH v5 6/7] platform/chrome: Create sysfs attributes for the ChromeOS EC Javier Martinez Canillas
2015-02-02 11:26 ` [PATCH v5 7/7] platform/chrome: Expose Chrome OS Lightbar to users Javier Martinez Canillas
2015-02-16 8:19 ` [PATCH v5 0/7] platform/chrome: Add user-space dev inferface support Javier Martinez Canillas
2015-02-18 2:26 ` Simon Glass
2015-02-18 9:27 ` Javier Martinez Canillas
2015-02-26 0:59 ` Olof Johansson
2015-02-26 16:00 ` Simon Glass
2015-02-26 0:57 ` Olof Johansson
2015-02-26 23:35 ` Gwendal Grignou
2015-02-27 0:11 ` Olof Johansson
2015-02-27 5:17 ` Javier Martinez Canillas
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=54EEE28F.8000307@collabora.co.uk \
--to=javier.martinez@collabora.co.uk \
--cc=corbet@lwn.net \
--cc=dianders@chromium.org \
--cc=gwendal@chromium.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=pebolle@tiscali.nl \
--cc=sjg@google.com \
--cc=varkabhadram@gmail.com \
--cc=wfrichar@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.