hwmon: Add support for W83667HG-B
in [Kernel]
|
Prev: macbook webcam no longer works on .35-rc
Next: e1000e: receives no packets after resume (2.6.35-rc3-00262-g984bc96)
From: Guenter Roeck on 2 Jul 2010 12:20 On Fri, Jul 02, 2010 at 10:59:03AM -0400, Jean Delvare wrote: > On Fri, 2 Jul 2010 07:09:44 -0700, Guenter Roeck wrote: > > On Fri, Jul 02, 2010 at 05:51:23AM -0400, Jean Delvare wrote: > > > On Fri, 2 Jul 2010 01:31:44 -0700, Guenter Roeck wrote: > > > > On Fri, Jul 02, 2010 at 04:13:45AM -0400, Jean Delvare wrote: > > > > > On Fri, 2 Jul 2010 01:07:04 -0700, Guenter Roeck wrote: > > > > > > I'll also add a check for the HG-I. > > > > > > > > > > Do you have a datasheet for that one too? > > > > > > > > > No. However, since we have a tester, we will have test coverage, > > > > so I figured it should be worth a try. If it doesn't work > > > > I can still drop it from the final patch. > > > > > > FYI, I have a datasheet, which unfortunately I am not allowed to share. > > > Please let me know if you want me to look up something for you. > > > > > How about the changed registers ? Would give us an idea if the chip is closer to > > 667 or to 667-B. > > There is no summary of this available. The only way is to go through > both datasheets and compare all registers in sequence. This takes time, > which is exactly why I couldn't find the time to do it :( > Yes, I noticed. Changes can be quite subtle, too. I'll remove the HG-I chip detection from the next patch rev unless I manage to get a datasheet as well. Guenter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Jean Delvare on 3 Jul 2010 03:50 On Fri, 2 Jul 2010 09:15:21 -0700, Guenter Roeck wrote: > On Fri, Jul 02, 2010 at 10:59:03AM -0400, Jean Delvare wrote: > > On Fri, 2 Jul 2010 07:09:44 -0700, Guenter Roeck wrote: > > > On Fri, Jul 02, 2010 at 05:51:23AM -0400, Jean Delvare wrote: > > > > FYI, I have a datasheet, which unfortunately I am not allowed to share. > > > > Please let me know if you want me to look up something for you. > > > > > > > How about the changed registers ? Would give us an idea if the chip is closer to > > > 667 or to 667-B. > > > > There is no summary of this available. The only way is to go through > > both datasheets and compare all registers in sequence. This takes time, > > which is exactly why I couldn't find the time to do it :( > > > Yes, I noticed. Changes can be quite subtle, too. > > I'll remove the HG-I chip detection from the next patch rev > unless I manage to get a datasheet as well. I agree. The 667HG-B support seems to be easier to get, and more urgent too, judging by the number of requests. Let's get this tested and upstream first, and then we see what can be done for the 677HG-I. -- Jean Delvare -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Jean Delvare on 3 Jul 2010 04:10 Hi Guenter, On Fri, 2 Jul 2010 07:54:04 -0700, Guenter Roeck wrote: > On Fri, Jul 02, 2010 at 05:49:49AM -0400, Jean Delvare wrote: > > On Fri, 2 Jul 2010 01:25:30 -0700, Guenter Roeck wrote: > > > After removing the defines and trying to compile I remembered. > > > I _knew_ there was a reason for not removing them. > > > Guess it's too late (or early) here to do serious work. > > > > > > The defines _are_ used, in: > > > > > > fan_functions(fan_max_output, FAN_MAX_OUTPUT) > > > fan_functions(fan_step_output, FAN_STEP_OUTPUT) > > > > > > which expands to W83627EHF_REG_FAN_MAX_OUTPUT and W83627EHF_REG_FAN_STEP_OUTPUT. > > > > > > Tricky ... and that was also the reason why I retained the original > > > global variables. > > > > Tricky indeed. We normally don't accept code like this in the kernel. > > > > > I'll move the pointers into per-device code as you suggested, but I'll > > > have to think about how to do that w/o having to change a lot of code. > > > > If code changes are desirable, let's just do them. You can do that in a > > preliminary patch, and then your patch adding support for the > > W83667HG-B goes on top of it. > > > Without the support for -B the changes are not really needed, so that patch > would not make much sense without it. It is still a good practice to split patches in this case. This makes review and bisection easier. Simply, we don't get to apply the first patch if we don't also apply the second. > Have you looked at v2 of the patch ? Not yet, will do now. > > > As for the 0xff - that pretty much applies to all chips supported by this driver. > > > I guess it is supposed to mean "not supported", and as a result the code will > > > write to a non-existing register. I don't really want to touch that. > > > > I want you to touch that. Writing to non-existing registers is a bad > > idea. You never know what actually happens when you do that. > > Good point. BTW, as I wasn't clear enough about this originally: I didn't mean this to fix to be included into your W83667HG-B support patch. It should be a separate patch, so that it can be easily backported. > Clean fix would be not to provide the unsupported attributes. Simple workaround > would be to return an error if a write is attempted on a non-supported attribute. > I am sure it would be better to not provide the attribute, but would you accept > the workaround ? I will accept whatever you are willing to provide. As you're the one spending the time, I'm not the one deciding how much you spend. > > > The size difference (3 entries vs. 4) doesn't matter, since the chips are both > > > configured to have only three pwm fan controllers (even though the W83667HG > > > is supposed to have four per its datasheet). So the 4th element of the arrays > > > will not be accessed by the code if W83667HG(-B) is detected. > > > > OK. > > On a side note, any idea why the 4th pwm is disabled for the W83667HG ? The W83667HG chip has only 3 FANOUT pins (98, 125 and 127), so it is expected that the driver exposes only 3 pwm outputs for this chip. I don't understand why you think it is a problem? Pin 98 can be used for an alternative function, so the corresponding pwm output should not even be unconditionally instantiated. Now the chip is quite complex in that it apparently has 4 fan control units, and which one controls which fan output can be decided by register values. I have no idea why they made it so complex at the hardware level, but this certainly explains why the driver is a little messy in this respect. We might have to move 667HG and later support to a separate driver at some point, I don't know. Now I'm sure you understand why I never took the time to look into adding W83667HG-B support ;) -- Jean Delvare -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Guenter Roeck on 3 Jul 2010 10:40
On Sat, Jul 03, 2010 at 04:09:10AM -0400, Jean Delvare wrote: > Hi Guenter, > > On Fri, 2 Jul 2010 07:54:04 -0700, Guenter Roeck wrote: > > On Fri, Jul 02, 2010 at 05:49:49AM -0400, Jean Delvare wrote: > > > On Fri, 2 Jul 2010 01:25:30 -0700, Guenter Roeck wrote: > > > > After removing the defines and trying to compile I remembered. > > > > I _knew_ there was a reason for not removing them. > > > > Guess it's too late (or early) here to do serious work. > > > > > > > > The defines _are_ used, in: > > > > > > > > fan_functions(fan_max_output, FAN_MAX_OUTPUT) > > > > fan_functions(fan_step_output, FAN_STEP_OUTPUT) > > > > > > > > which expands to W83627EHF_REG_FAN_MAX_OUTPUT and W83627EHF_REG_FAN_STEP_OUTPUT. > > > > > > > > Tricky ... and that was also the reason why I retained the original > > > > global variables. > > > > > > Tricky indeed. We normally don't accept code like this in the kernel. > > > > > > > I'll move the pointers into per-device code as you suggested, but I'll > > > > have to think about how to do that w/o having to change a lot of code. > > > > > > If code changes are desirable, let's just do them. You can do that in a > > > preliminary patch, and then your patch adding support for the > > > W83667HG-B goes on top of it. > > > > > Without the support for -B the changes are not really needed, so that patch > > would not make much sense without it. > > It is still a good practice to split patches in this case. This makes > review and bisection easier. Simply, we don't get to apply the first > patch if we don't also apply the second. > > > Have you looked at v2 of the patch ? > > Not yet, will do now. > > > > > As for the 0xff - that pretty much applies to all chips supported by this driver. > > > > I guess it is supposed to mean "not supported", and as a result the code will > > > > write to a non-existing register. I don't really want to touch that. > > > > > > I want you to touch that. Writing to non-existing registers is a bad > > > idea. You never know what actually happens when you do that. > > > > Good point. > > BTW, as I wasn't clear enough about this originally: I didn't mean this > to fix to be included into your W83667HG-B support patch. It should be > a separate patch, so that it can be easily backported. > Actually, turns out the 0xff register values are not a problem. sysfs attribute files for max and step registers are only created for fan 2 and 4, but not for fan 1 and 3. Thus, the 0xff array entries will not be used. I'll have to change that for rev -B, because those registers _do_ exist there, and the files should exist. > > Clean fix would be not to provide the unsupported attributes. Simple workaround > > would be to return an error if a write is attempted on a non-supported attribute. > > I am sure it would be better to not provide the attribute, but would you accept > > the workaround ? > > I will accept whatever you are willing to provide. As you're the one > spending the time, I'm not the one deciding how much you spend. > > > > > The size difference (3 entries vs. 4) doesn't matter, since the chips are both > > > > configured to have only three pwm fan controllers (even though the W83667HG > > > > is supposed to have four per its datasheet). So the 4th element of the arrays > > > > will not be accessed by the code if W83667HG(-B) is detected. > > > > > > OK. > > > > On a side note, any idea why the 4th pwm is disabled for the W83667HG ? > > The W83667HG chip has only 3 FANOUT pins (98, 125 and 127), so it is > expected that the driver exposes only 3 pwm outputs for this chip. I > don't understand why you think it is a problem? > Not a problem. Just wondering. Guenter > Pin 98 can be used for an alternative function, so the corresponding > pwm output should not even be unconditionally instantiated. > > Now the chip is quite complex in that it apparently has 4 fan control > units, and which one controls which fan output can be decided by > register values. I have no idea why they made it so complex at the > hardware level, but this certainly explains why the driver is a little > messy in this respect. We might have to move 667HG and later support to > a separate driver at some point, I don't know. > > Now I'm sure you understand why I never took the time to look into > adding W83667HG-B support ;) > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |