All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Vinay Simha B N <simhavcs@gmail.com>
Cc: jdelvare@suse.com, linux-hwmon@vger.kernel.org
Subject: Re: tmp102 hwmon accessing temp1_input, max, max_hyst
Date: Thu, 21 Feb 2019 09:55:11 -0800	[thread overview]
Message-ID: <20190221175511.GA22715@roeck-us.net> (raw)
In-Reply-To: <CAGWqDJ48N5Q6OsHq_f217za-34zQMDY8qNL6XEDLREPY3JP3MA@mail.gmail.com>

On Thu, Feb 21, 2019 at 08:21:09PM +0530, Vinay Simha B N wrote:
> hi,
> 
> could you please suggest, how to export_symbol the tmp102 temp1_input, max
> and max_hyst values to another kernel driver?
> 
> We can acess the values
> from filp_open("/sys/class/hwmon/hwmon1/temp1_input", O_RDONLY, 0); in
> kernel space, but is there better apporach to access the values in the
> kernel space.
> 
There is no in-kernel API to do that, and I do not immediately see
the purpose. Either case, accessing the sysfs attribute directly is
as wrong as it can get, if for nothing else since there is no guarantee
that this will always be the hwmon1 device.

Can you explain what you are trying to do ?

Thanks,
Guenter

  parent reply	other threads:[~2019-02-21 17:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGWqDJ48N5Q6OsHq_f217za-34zQMDY8qNL6XEDLREPY3JP3MA@mail.gmail.com>
2019-02-21 15:47 ` tmp102 hwmon accessing temp1_input, max, max_hyst Vinay Simha B N
2019-02-21 17:55 ` Guenter Roeck [this message]
2019-02-21 18:16   ` Vinay Simha B N
2019-02-21 18:48     ` Guenter Roeck
2019-02-21 19:02       ` Vinay Simha B N
2019-02-21 19:49         ` Guenter Roeck
2019-02-25 10:30           ` Vinay Simha B N
2019-02-25 15:19             ` Vinay Simha B N
2019-02-27  6:44             ` Vinay Simha B N
2019-02-27 20:49               ` Guenter Roeck
2019-04-02  8:36                 ` Vinay Simha B N
2019-04-02 13:28                   ` Guenter Roeck

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=20190221175511.GA22715@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=simhavcs@gmail.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 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.