From: Martin Peres <martin.peres-GANU6spQydw@public.gmane.org> To: Dave Airlie <airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> Cc: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>, nouveau <Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>, Guenter Roeck <guenter.roeck-IzeFyvvaP7pWk0Htik3J/w@public.gmane.org>, lm-sensors-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org Subject: Re: [lm-sensors] hwmon API update Date: Thu, 03 Mar 2011 14:09:54 +0100 [thread overview] Message-ID: <4D6F9322.3080209@free.fr> (raw) In-Reply-To: <AANLkTindG=m4FhNS202MH8YVBUCoDEADTQLxo-Bf_8qx-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> Dave, The answers are inlined. Le 03/03/2011 10:36, Dave Airlie a écrit : > Martin, > > you probably should have cc'ed Matthew since it was his patch you based this on, > and I think he can provide a good explaination. I knew he was monitoring the nouveau ML. He provided a good explanation but forgot to CC the nouveau ML. Could someone in the lm-sensors mailing list forward the most important thread? > to clarify some points, > > radeon does probably want something exactly like this, we just haven't gotten to > it completely yet, I'd rather not have two drivers in the kernel for > exact same hardware, > and I believe sharing the hwmon code to do what we want is a good plan since you > don't go around reinventing wheels, but if hwmon/i2c maintainers have > no interest > it leaves with little choice but to implement about 5-10 i2c drivers > again in drm codebase. > > Maybe hwmon/i2c maintainers could suggest a cleaner way to implement > what we want, > which I think I can summarize as > > a) access to monitored values in-kernel > b) no userspace access to the same values except via sanitised via the driver. a) is mandatory, b) would be great! > though I'm not following this as closely as I should so I may have > missed something. I don't think you missed anything but long argue on the lm-sensors ML. > Dave. The reason why I didn't answer on this matter earlier was that I was in the process of moving from one city to another. I only got the internet access on both my computers yesterday evening and I was planing to restart the process this week end. It's good to see you we are not the only one needing this. Martin
WARNING: multiple messages have this Message-ID (diff)
From: Martin Peres <martin.peres@free.fr> To: Dave Airlie <airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> Cc: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>, nouveau <Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>, Guenter Roeck <guenter.roeck-IzeFyvvaP7pWk0Htik3J/w@public.gmane.org>, lm-sensors-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org Subject: Re: [lm-sensors] [Nouveau] hwmon API update Date: Thu, 03 Mar 2011 13:09:54 +0000 [thread overview] Message-ID: <4D6F9322.3080209@free.fr> (raw) In-Reply-To: <AANLkTindG=m4FhNS202MH8YVBUCoDEADTQLxo-Bf_8qx-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> Dave, The answers are inlined. Le 03/03/2011 10:36, Dave Airlie a écrit : > Martin, > > you probably should have cc'ed Matthew since it was his patch you based this on, > and I think he can provide a good explaination. I knew he was monitoring the nouveau ML. He provided a good explanation but forgot to CC the nouveau ML. Could someone in the lm-sensors mailing list forward the most important thread? > to clarify some points, > > radeon does probably want something exactly like this, we just haven't gotten to > it completely yet, I'd rather not have two drivers in the kernel for > exact same hardware, > and I believe sharing the hwmon code to do what we want is a good plan since you > don't go around reinventing wheels, but if hwmon/i2c maintainers have > no interest > it leaves with little choice but to implement about 5-10 i2c drivers > again in drm codebase. > > Maybe hwmon/i2c maintainers could suggest a cleaner way to implement > what we want, > which I think I can summarize as > > a) access to monitored values in-kernel > b) no userspace access to the same values except via sanitised via the driver. a) is mandatory, b) would be great! > though I'm not following this as closely as I should so I may have > missed something. I don't think you missed anything but long argue on the lm-sensors ML. > Dave. The reason why I didn't answer on this matter earlier was that I was in the process of moving from one city to another. I only got the internet access on both my computers yesterday evening and I was planing to restart the process this week end. It's good to see you we are not the only one needing this. Martin _______________________________________________ lm-sensors mailing list lm-sensors@lm-sensors.org http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2011-03-03 13:09 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-02-13 12:18 hwmon API update Martin Peres 2011-02-13 12:18 ` [lm-sensors] " Martin Peres 2011-02-13 17:16 ` Guenter Roeck 2011-02-13 17:16 ` [lm-sensors] " Guenter Roeck 2011-02-13 20:00 ` Martin Peres 2011-02-13 20:00 ` [lm-sensors] " Martin Peres 2011-02-13 22:08 ` Jean Delvare 2011-02-13 22:08 ` [lm-sensors] " Jean Delvare [not found] ` <20110213230833.0ee2ff16-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org> 2011-03-03 9:36 ` Dave Airlie 2011-03-03 9:36 ` [lm-sensors] [Nouveau] " Dave Airlie [not found] ` <AANLkTindG=m4FhNS202MH8YVBUCoDEADTQLxo-Bf_8qx-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2011-03-03 13:09 ` Martin Peres [this message] 2011-03-03 13:09 ` Martin Peres 2011-03-03 15:22 ` Guenter Roeck 2011-03-03 15:22 ` [lm-sensors] " Guenter Roeck [not found] ` <20110303152216.GA21667-IzeFyvvaP7pWk0Htik3J/w@public.gmane.org> 2011-03-03 17:29 ` [lm-sensors] " Martin Peres 2011-03-03 17:29 ` [lm-sensors] [Nouveau] " Martin Peres [not found] ` <4D6FCFF2.7040604-GANU6spQydw@public.gmane.org> 2011-03-03 20:48 ` [lm-sensors] " Lucas Stach 2011-03-03 20:48 ` [lm-sensors] [Nouveau] " Lucas Stach 2011-03-03 21:19 ` Guenter Roeck 2011-03-03 21:19 ` [lm-sensors] " Guenter Roeck 2011-03-03 21:56 ` [lm-sensors] " Lucas Stach 2011-03-03 21:56 ` [lm-sensors] [Nouveau] " Lucas Stach 2011-03-03 22:03 ` [lm-sensors] " Guenter Roeck 2011-03-03 22:03 ` [lm-sensors] [Nouveau] " Guenter Roeck 2011-03-03 23:53 ` [lm-sensors] " Martin Peres 2011-03-03 23:53 ` [lm-sensors] [Nouveau] " Martin Peres [not found] ` <4D7029E8.4040706-GANU6spQydw@public.gmane.org> 2011-03-04 0:59 ` [lm-sensors] " Guenter Roeck 2011-03-04 0:59 ` [lm-sensors] [Nouveau] " Guenter Roeck [not found] ` <20110304005900.GB31318-IzeFyvvaP7pWk0Htik3J/w@public.gmane.org> 2011-03-04 8:36 ` [lm-sensors] " Martin Peres 2011-03-04 8:36 ` [lm-sensors] [Nouveau] " Martin Peres 2011-02-14 16:23 ` [lm-sensors] " Matthew Garrett 2011-02-14 18:19 ` Guenter Roeck 2011-02-14 18:22 ` Matthew Garrett 2011-02-14 19:01 ` Guenter Roeck 2011-02-14 19:05 ` Matthew Garrett 2011-02-14 19:33 ` Guenter Roeck 2011-02-14 19:40 ` Matthew Garrett 2011-02-14 21:25 ` Guenter Roeck 2011-02-14 21:29 ` Matthew Garrett 2011-02-15 21:50 ` Jean Delvare 2011-02-15 22:07 ` Jean Delvare 2011-02-15 22:23 ` Guenter Roeck 2011-02-28 17:50 ` Lucas Stach 2011-02-28 18:42 ` Guenter Roeck 2011-02-28 23:24 ` Lucas Stach 2011-10-10 22:29 ` Kristen Eisenberg
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=4D6F9322.3080209@free.fr \ --to=martin.peres-ganu6spqydw@public.gmane.org \ --cc=Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \ --cc=airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \ --cc=guenter.roeck-IzeFyvvaP7pWk0Htik3J/w@public.gmane.org \ --cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \ --cc=lm-sensors-GZX6beZjE8VD60Wz+7aTrA@public.gmane.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: linkBe 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.