<feed xmlns='http://www.w3.org/2005/Atom'>
<title>BMC/Intel-BMC/linux.git/drivers/mfd, branch dev-5.10-intel</title>
<subtitle>Intel OpenBMC Linux kernel source tree (mirror)</subtitle>
<id>https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev-5.10-intel</id>
<link rel='self' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev-5.10-intel'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/'/>
<updated>2021-08-02T16:04:00+00:00</updated>
<entry>
<title>mfd: intel-peci-client: Extend MFD cell id with additional parameter</title>
<updated>2021-08-02T16:04:00+00:00</updated>
<author>
<name>Iwona Winiarska</name>
<email>iwona.winiarska@intel.com</email>
</author>
<published>2021-07-02T14:10:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=d2910d58808814fb492e76f592e30fbba963da85'/>
<id>urn:sha1:d2910d58808814fb492e76f592e30fbba963da85</id>
<content type='text'>
If we're only using CPU number as MFD cell id, we don't have a way to
avoid a collision in case we have multiple adapters able to communicate
with the same CPUs.

[  794.916872] sysfs: cannot create duplicate filename '/bus/platform/devices/peci-cputemp.0'
[  795.452507] intel_peci_client 1-30: Failed to register child devices: -17
[  795.460238] intel_peci_client: probe of 1-30 failed with error -17

To fix this problem, let's use both adapter number and cpu number to
calculate MFD cell id.

Change-Id: If0559a0b629081e6201b4ce93cb8bc649dd2a258
Signed-off-by: Iwona Winiarska &lt;iwona.winiarska@intel.com&gt;
</content>
</entry>
<entry>
<title>mfd: peci: Add ICX-D generation info</title>
<updated>2021-08-02T16:04:00+00:00</updated>
<author>
<name>Saravanan Palanisamy</name>
<email>saravanan.palanisamy@intel.com</email>
</author>
<published>2020-05-15T17:40:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=54a75bfb531163eaaa417e0a220648f910019203'/>
<id>urn:sha1:54a75bfb531163eaaa417e0a220648f910019203</id>
<content type='text'>
This commit adds CPU generation info for ICX-D Xeon family.

Signed-off-by: Saravanan Palanisamy &lt;saravanan.palanisamy@intel.com&gt;
Signed-off-by: Anoop S &lt;anoopx.s@intel.com&gt;
</content>
</entry>
<entry>
<title>mfd: peci: Add ICX generation info</title>
<updated>2021-08-02T16:04:00+00:00</updated>
<author>
<name>Jae Hyun Yoo</name>
<email>jae.hyun.yoo@intel.com</email>
</author>
<published>2018-11-07T00:25:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=5d75974bcb651fd5eec7abad65e12fbc2dad7a0a'/>
<id>urn:sha1:5d75974bcb651fd5eec7abad65e12fbc2dad7a0a</id>
<content type='text'>
This commit adds CPU generation info for ICX family.

Signed-off-by: Jae Hyun Yoo &lt;jae.hyun.yoo@intel.com&gt;
</content>
</entry>
<entry>
<title>hwmon: peci: dimmpower implementation</title>
<updated>2021-08-02T16:04:00+00:00</updated>
<author>
<name>Zbigniew Lukwinski</name>
<email>zbigniew.lukwinski@linux.intel.com</email>
</author>
<published>2020-06-17T06:12:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=3d7b07b8a3a68b3ae13c7ddb53e2fee890515b37'/>
<id>urn:sha1:3d7b07b8a3a68b3ae13c7ddb53e2fee890515b37</id>
<content type='text'>
1. Peci dimmpower module implementation.
2. Enable DIMM avarage power, power limit, power limit max setting,
   power limit min setting reading and expose them under
   power1_avarage, power1_cap, power1_cap_max, power1_cap_min in
   sysfs.
3. Enable DIMM power limit writing through power1_cap.

Tested:
 * on WilsonCity platform,
 * power1_avarage, power1_cap, power1_cap_max and power1_cap_min work
   as expected

Signed-off-by: Zbigniew Lukwinski &lt;zbigniew.lukwinski@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Add peci-cpupower driver</title>
<updated>2021-08-02T16:04:00+00:00</updated>
<author>
<name>ZhikuiRen</name>
<email>zhikui.ren@intel.com</email>
</author>
<published>2020-01-09T18:48:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=c2dee3025fab0e899f6f38ea5970943039b02437'/>
<id>urn:sha1:c2dee3025fab0e899f6f38ea5970943039b02437</id>
<content type='text'>
peci-cpupower reads CPU energy counter through peci
and computes average power in mW since last read.

Signed-off-by: ZhikuiRen &lt;zhikui.ren@intel.com&gt;
</content>
</entry>
<entry>
<title>mfd: intel-peci-client: Add Intel PECI client driver</title>
<updated>2021-08-02T16:04:00+00:00</updated>
<author>
<name>Jae Hyun Yoo</name>
<email>jae.hyun.yoo@linux.intel.com</email>
</author>
<published>2019-12-18T01:28:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=8efcec506c6aa0159179ae0e7a759afc52347d3b'/>
<id>urn:sha1:8efcec506c6aa0159179ae0e7a759afc52347d3b</id>
<content type='text'>
This commit adds Intel PECI client driver.

Signed-off-by: Jae Hyun Yoo &lt;jae.hyun.yoo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>mfd: cpcap: Fix cpcap dmamask not set warnings</title>
<updated>2021-07-20T14:05:42+00:00</updated>
<author>
<name>Tony Lindgren</name>
<email>tony@atomide.com</email>
</author>
<published>2021-05-22T05:10:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=af8b891cd339863bfc4c8d7581acaed8d30cc280'/>
<id>urn:sha1:af8b891cd339863bfc4c8d7581acaed8d30cc280</id>
<content type='text'>
[ Upstream commit 0b7cbe811ca524295ea43d9a4d73d3427e419c54 ]

We have started to get a bunch of pointless dmamask not set warnings
that makes the output of dmesg -l err,warn hard to read with many
extra warnings:

cpcap-regulator cpcap-regulator.0: DMA mask not set
cpcap_adc cpcap_adc.0: DMA mask not set
cpcap_battery cpcap_battery.0: DMA mask not set
cpcap-charger cpcap-charger.0: DMA mask not set
cpcap-pwrbutton cpcap-pwrbutton.0: DMA mask not set
cpcap-led cpcap-led.0: DMA mask not set
cpcap-led cpcap-led.1: DMA mask not set
cpcap-led cpcap-led.2: DMA mask not set
cpcap-led cpcap-led.3: DMA mask not set
cpcap-led cpcap-led.4: DMA mask not set
cpcap-rtc cpcap-rtc.0: DMA mask not set
cpcap-usb-phy cpcap-usb-phy.0: DMA mask not set

This seems to have started with commit 4d8bde883bfb ("OF: Don't set
default coherent DMA mask"). We have the parent SPI controller use
DMA, while CPCAP driver and it's children do not. For audio, the
DMA is handled over I2S bus with the McBSP driver.

Cc: Carl Philipp Klemm &lt;philipp@uvos.xyz&gt;
Cc: Ivan Jelincic &lt;parazyd@dyne.org&gt;
Cc: Merlijn Wajer &lt;merlijn@wizzup.org&gt;
Cc: Pavel Machek &lt;pavel@ucw.cz&gt;
Cc: Sebastian Reichel &lt;sre@kernel.org&gt;
Cc: Sicelo A. Mhlongo &lt;absicsz@gmail.com&gt;
Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;
Signed-off-by: Lee Jones &lt;lee.jones@linaro.org&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>mfd: da9052/stmpe: Add and modify MODULE_DEVICE_TABLE</title>
<updated>2021-07-20T14:05:41+00:00</updated>
<author>
<name>Zou Wei</name>
<email>zou_wei@huawei.com</email>
</author>
<published>2021-05-12T06:33:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=d339f6a0d1a1be81070159636643dc64f9177682'/>
<id>urn:sha1:d339f6a0d1a1be81070159636643dc64f9177682</id>
<content type='text'>
[ Upstream commit 4700ef326556ed74aba188f12396740a8c1c21dd ]

This patch adds/modifies MODULE_DEVICE_TABLE definition which generates
correct modalias for automatic loading of this driver when it is built
as an external module.

Reported-by: Hulk Robot &lt;hulkci@huawei.com&gt;
Signed-off-by: Zou Wei &lt;zou_wei@huawei.com&gt;
Signed-off-by: Lee Jones &lt;lee.jones@linaro.org&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>mfd: syscon: Free the allocated name field of struct regmap_config</title>
<updated>2021-07-19T07:45:00+00:00</updated>
<author>
<name>Limeng</name>
<email>Meng.Li@windriver.com</email>
</author>
<published>2021-04-07T05:25:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=f0a079c0ba87e829058469012cb211b8cc388d04'/>
<id>urn:sha1:f0a079c0ba87e829058469012cb211b8cc388d04</id>
<content type='text'>
commit 56a1188159cb2b87fbcb5a7a7afb38a4dd9db0c1 upstream.

The commit 529a1101212a("mfd: syscon: Don't free allocated name
for regmap_config") doesn't free the allocated name field of struct
regmap_config, but introduce a memory leak. There is another
commit 94cc89eb8fa5("regmap: debugfs: Fix handling of name string
for debugfs init delays") fixing this debugfs init issue from root
cause. With this fixing, the name field in struct regmap_debugfs_node
is removed. When initialize debugfs for syscon driver, the name
field of struct regmap_config is not used anymore. So, the allocated
name field of struct regmap_config is need to be freed directly after
regmap initialization to avoid memory leak.

Cc: stable@vger.kernel.org
Fixes: 529a1101212a("mfd: syscon: Don't free allocated name for regmap_config")
Signed-off-by: Meng Li &lt;Meng.Li@windriver.com&gt;
Signed-off-by: Lee Jones &lt;lee.jones@linaro.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>mfd: rn5t618: Fix IRQ trigger by changing it to level mode</title>
<updated>2021-07-14T14:56:40+00:00</updated>
<author>
<name>Andreas Kemnade</name>
<email>andreas@kemnade.info</email>
</author>
<published>2021-05-15T20:55:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=d22bef41017b4edfb0111c30f8bc476c17b5d720'/>
<id>urn:sha1:d22bef41017b4edfb0111c30f8bc476c17b5d720</id>
<content type='text'>
[ Upstream commit a1649a5260631979c68e5b2012f60f90300e646f ]

During more massive generation of interrupts, the IRQ got stuck,
and the subdevices did not see any new interrupts. That happens
especially at wonky USB supply in combination with ADC reads.
To fix that trigger the IRQ at level low instead of falling edge.

Fixes: 0c81604516af ("mfd: rn5t618: Add IRQ support")
Signed-off-by: Andreas Kemnade &lt;andreas@kemnade.info&gt;
Signed-off-by: Lee Jones &lt;lee.jones@linaro.org&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
</feed>
