All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Akira Shimahara <akira215corp@gmail.com>
Cc: zbr@ioremap.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Changes in w1_therm.c and adding w1_therm.h
Date: Thu, 23 Apr 2020 16:41:16 +0200	[thread overview]
Message-ID: <20200423144116.GA7319@kroah.com> (raw)
In-Reply-To: <20200414170248.299534-1-akira215corp@gmail.com>

On Tue, Apr 14, 2020 at 07:02:48PM +0200, Akira Shimahara wrote:
> From: Akira SHIMAHARA <akira215corp@gmail.com>
> 
> Patch for enhacement of w1_therm module. Added features :
>  - Bulk read : send one command for all the slaves 
>  		on the bus to trigger temperature conversion
>  - Optimized conversion time regarding to device resolution
>  - Dedicated sysfs entry for powering read,
>  		resolution set/get, eeprom save/restore
>  - Alarms settings and reading
>  - Code optimization to mitigate bus traffic
>  		(devices information are stored to avoid
> 		interrogating each device every-time)
> 
> Following sysfs entry are added :
>  - temperature (RO) : return the temperature in 1/1000°
>  - ext_power (RO) : return the power status of the device
>  - resolution (RW) : get or set the device resolution (supported devices)
>  - eeprom (WO) :trigger a save or restore to/from device EEPROM
>  - alarms (RW) : read or write TH and TL in the device RAM
>  - therm_bulk_read (RW) : Attribute at master level to trigger 
>  		bulk read and to survey the progress of devices conversions
>  - w1_slave has been kept for compatibility

You do not document any of these new sysfs files, why not?

Please add entries to Documentation/ABI/

And for the temp and other issues, shouldn't you use the "default"
kernel subsystems instead of creating your own api here?

thanks,

greg k-h

  parent reply	other threads:[~2020-04-23 14:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-14 17:02 [PATCH] Changes in w1_therm.c and adding w1_therm.h Akira Shimahara
2020-04-16 20:12 ` Evgeniy Polyakov
2020-04-17 13:04   ` akira215
2020-04-23 14:41 ` Greg KH [this message]
2020-04-23 17:07   ` Evgeniy Polyakov
2020-04-23 17:59     ` Akira shimahara
2020-04-23 18:16       ` Evgeniy Polyakov
2020-04-25 15:31   ` [PATCH v2 1/2] " Akira Shimahara
2020-04-26  7:51     ` Greg KH
2020-04-26 12:36       ` Akira shimahara
2020-04-26 17:09         ` Greg KH
2020-04-26 17:20           ` Akira shimahara
2020-04-28 12:44             ` Greg KH
2020-04-28 13:42               ` Akira shimahara

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=20200423144116.GA7319@kroah.com \
    --to=greg@kroah.com \
    --cc=akira215corp@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zbr@ioremap.net \
    /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.