[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200430112131.GA2945965@kroah.com>
Date: Thu, 30 Apr 2020 13:21:31 +0200
From: Greg KH <greg@...ah.com>
To: Akira shimahara <akira215corp@...il.com>
Cc: Evgeniy Polyakov <zbr@...emap.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 2/5] w1_therm: adding sysfs entry to check device power
On Thu, Apr 30, 2020 at 12:34:03PM +0200, Akira shimahara wrote:
> Hello,
>
> Le mercredi 29 avril 2020 à 18:18 +0300, Evgeniy Polyakov a écrit :
> > Hi
> >
> >
> >
> > 29.04.2020, 16:47, "Greg KH" <greg@...ah.com>:
> >
> >
> >
> > > > +What: /sys/bus/w1/devices/.../w1_slave
> > > > +Date: Apr 2020
> > > > +Contact: Akira Shimahara <akira215corp@...il.com>
> > > > +Description:
> > > > + (RW) return the temperature in 1/1000 degC.
> > > > + *read*: return 2 lines with the hexa output data sent on the
> > > > + bus, return the CRC check and temperature in 1/1000 degC
> > > the w1_slave file returns a temperature???
> > > And sysfs is 1 value-per-file, not multiple lines.
> >
> >
> > It was 'content crc' previously, and probably a good idea would be to
> > add just one file with 'content'
>
> That's the purpose of the new sysfs entry 'temperature'. It only
> content temperature. As already mentionned we have to keep the w1_slave
> entry for compatibility purpose, all existing user application parse
> this file.
That's fine, but the document you wrote here says the file is called
"w1_slave", not "temperature" :)
Powered by blists - more mailing lists