From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Ping Cheng <pinglinux@gmail.com>, Jiri Kosina <jkosina@suse.cz>,
Jason Gerecke <killertofu@gmail.com>,
Przemo Firszt <przemo@firszt.eu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-input <linux-input@vger.kernel.org>
Subject: Re: [PATCH] Input - wacom: update the ABI doc according to latest changes
Date: Wed, 6 Aug 2014 14:36:51 -0700 [thread overview]
Message-ID: <20140806213651.GD22889@core.coreip.homeip.net> (raw)
In-Reply-To: <20140806212902.GD15018@mail.corp.redhat.com>
On Wed, Aug 06, 2014 at 05:29:02PM -0400, Benjamin Tissoires wrote:
> On Aug 06 2014 or thereabouts, Dmitry Torokhov wrote:
> > On Wed, Aug 06, 2014 at 04:44:08PM -0400, Benjamin Tissoires wrote:
> > > On Aug 05 2014 or thereabouts, Ping Cheng wrote:
> > > > On Tue, Aug 5, 2014 at 2:34 PM, Benjamin Tissoires
> > > > <benjamin.tissoires@redhat.com> wrote:
> > > > > Hi Ping,
> > > > >
> > > > > On Aug 05 2014 or thereabouts, Ping Cheng wrote:
> > > > >> Thank you Benjamin for updating the ABI docs. My comments are inline.
> > > > >>
> > > > >> With those lines updated, this patch is:
> > > > >>
> > > > >> Reviewed-by: Ping Cheng <pingc@wacom.com>
> > > > >
> > > > > Thanks!
> > > > >
> > > > >>
> > > > >> Cheers,
> > > > >>
> > > > >> Ping
> > > > >>
> > > > >> On Tue, Aug 5, 2014 at 8:34 AM, Benjamin Tissoires
> > > > >> <benjamin.tissoires@redhat.com> wrote:
> > > > >> > Now the devices show up under hid no matter the connection. So update the
> > > > >> > sysfs path to the shortest and common one.
> > > > >> > The ABI has also been unified regarding the OLEDs, but Bluetooth handle
> > > > >> > only 1-bit images instead of 4.
> > > > >> >
> > > > >> > Signed-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
> > > > >> > ---
> > > > >> >
> > > > >> > Guys,
> > > > >> >
> > > > >> > by updating this and working on the g-s-d client side for OLEDs, I think now
> > > > >> > that we should also keep the oled*_img for Bluetooth and implement this file
> > > > >> > for USB too. The user space code gets messy quite fast due to the need to
> > > > >> > support old and new kernels, whereas if we handle the scrambling in the kernel,
> > > > >> > it should be quite straightforward.
> > > > >> > Of course, we have to keep the current button<n>_rawimg for backward
> > > > >> > compatibility.
> > > > >> >
> > > > >> > Any thoughts?
> > > > >> >
> > > > >> > Cheers,
> > > > >> > Benjamin
> > > > >> >
> > > > >> > Documentation/ABI/testing/sysfs-driver-wacom | 56 ++++++++++------------------
> > > > >> > 1 file changed, 20 insertions(+), 36 deletions(-)
> > > > >> >
> > > > >> > diff --git a/Documentation/ABI/testing/sysfs-driver-wacom b/Documentation/ABI/testing/sysfs-driver-wacom
> > > > >> > index 7fc7810..c75ed4c 100644
> > > > >> > --- a/Documentation/ABI/testing/sysfs-driver-wacom
> > > > >> > +++ b/Documentation/ABI/testing/sysfs-driver-wacom
> > > > >> > @@ -1,47 +1,26 @@
> > > > >> > -WWhat: /sys/class/hidraw/hidraw*/device/oled*_img
> > > > >> > -Date: June 2012
> > > > >> > -Contact: linux-bluetooth@vger.kernel.org
> > > > >> > -Description:
> > > > >> > - The /sys/class/hidraw/hidraw*/device/oled*_img files control
> > > > >> > - OLED mocro displays on Intuos4 Wireless tablet. Accepted image
> > > > >> > - has to contain 256 bytes (64x32 px 1 bit colour). The format
> > > > >> > - is the same as PBM image 62x32px without header (64 bits per
> > > > >> > - horizontal line, 32 lines). An example of setting OLED No. 0:
> > > > >> > - dd bs=256 count=1 if=img_file of=[path to oled0_img]/oled0_img
> > > > >> > - The attribute is read only and no local copy of the image is
> > > > >> > - stored.
> > > > >> > -
> > > > >> > -What: /sys/class/hidraw/hidraw*/device/speed
> > > > >> > +What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/speed
> > > > >> > Date: April 2010
> > > > >>
> > > > >> Should the Date be updated?
> > > > >
> > > > > I don't think that this one should. The ABI is the same since April
> > > > > 2010, and the "new" path works also for older kernels. So basically,
> > > > > here, for Bluetooth, there has been no changes.
> > > >
> > > > Oh, I see your point. But, don't we consider path part of the interface?
> > > >
> > >
> > > Well, in this case, both the path /sys/class/hidraw/hidraw*/device/speed
> > > and /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/speed refers to the same
> > > device, even in April 2010.
> > >
> > > /sys/class/hidraw/hidraw*/device is IMO not accurate because you have to
> > > check all the hidraw devices to find the right one.
> > > /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/speed gives you the correct
> > > at first sight. This is just a fix to have a more reliable path in the
> > > documentation, not a change.
> >
> > Can we document this in changelog?
> >
>
> Hmm, yes. I guess I'll have to send a new version with this
> documentation in the commit message and the update of the other dates.
>
> I should be offline for the next 3 to 4 hours, so it will have to wait
> tonight or tomorrow morning.
Well, it is a doc patch, it can go in at pretty much any time.
>
> BTW, thanks for merging the rest of the series (and the various
> patches). Greatly appreciated.
No, thank you for making them ;)
Thanks.
--
Dmitry
prev parent reply other threads:[~2014-08-06 21:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 15:34 [PATCH] Input - wacom: update the ABI doc according to latest changes Benjamin Tissoires
2014-08-05 15:53 ` Przemo Firszt
2014-08-05 21:18 ` Ping Cheng
2014-08-05 21:34 ` Benjamin Tissoires
2014-08-05 22:57 ` Ping Cheng
2014-08-06 20:44 ` Benjamin Tissoires
2014-08-06 21:04 ` Dmitry Torokhov
2014-08-06 21:29 ` Benjamin Tissoires
2014-08-06 21:36 ` Dmitry Torokhov [this message]
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=20140806213651.GD22889@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jkosina@suse.cz \
--cc=killertofu@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pinglinux@gmail.com \
--cc=przemo@firszt.eu \
/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).