<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/drivers, branch v2022.10-rc4</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/drivers?h=v2022.10-rc4</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/drivers?h=v2022.10-rc4'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2022-09-05T02:35:40Z</updated>
<entry>
<title>Merge tag 'u-boot-rockchip-20220905' of https://source.denx.de/u-boot/custodians/u-boot-rockchip</title>
<updated>2022-09-05T02:35:40Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2022-09-05T02:35:40Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=05f135ab3e4dfec47921588886c0a95b5275fc0e'/>
<id>urn:sha1:05f135ab3e4dfec47921588886c0a95b5275fc0e</id>
<content type='text'>
- migrate to use binman for U-Boot image generate on rockchip platform;
- Some fixes for rk3399 and rk3308;
</content>
</entry>
<entry>
<title>clk: rockchip: rk3399: Fix Unknown clock 77 on mmc@fe310000</title>
<updated>2022-09-04T12:00:39Z</updated>
<author>
<name>Michal Suchanek</name>
<email>msuchanek@suse.de</email>
</author>
<published>2022-08-21T07:17:24Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=f103c112660217f8875398435e47d545ba934a5c'/>
<id>urn:sha1:f103c112660217f8875398435e47d545ba934a5c</id>
<content type='text'>
Adding some debug prints I can see:

MMC:   mmc@fe320000: Got clock clock-controller@ff760000 76
mmc@fe310000: Got clock clock-controller@ff760000 77
Unknown clock 77
rockchip_dwmmc_get_mmc_clk: err=-2
mmc@fe310000: 3, mmc@fe320000: 1, mmc@fe330000: 0

According to kernel code the SDIO clock is identical to SDMMC clock
except for the con 16-&gt;15 change.

Add support for the clock to avoid the error.

Signed-off-by: Michal Suchanek &lt;msuchanek@suse.de&gt;
Reviewed-by: Kever Yang &lt;kever.yang@rock-chips.com&gt;
</content>
</entry>
<entry>
<title>ram: rk3399: Conduct memory training at 400MHz</title>
<updated>2022-09-04T12:00:38Z</updated>
<author>
<name>Lee Jones</name>
<email>lee@kernel.org</email>
</author>
<published>2022-08-11T07:58:48Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=337e92e79c95ffb8c0c6e7b4023c955c50fca018'/>
<id>urn:sha1:337e92e79c95ffb8c0c6e7b4023c955c50fca018</id>
<content type='text'>
Currently the default initialisation frequency is 50MHz.  Although
this does appear to be suitable for some LPDDR4 RAM chips, training at
this low frequency has been seen to cause Column errors, leading to
Capacity check errors on others.

Here we force RAM initialisation to happen at 400MHz before ramping up
to the final value running value of 800MHz after everything has been
successfully configured.

Link: https://lore.kernel.org/u-boot/Yo4v3jUeHXTovjOH@google.com/
Suggested-by: YouMin Chen &lt;cym@rock-chips.com&gt;
Signed-off-by: Lee Jones &lt;lee@kernel.org&gt;
Tested-by: Xavier Drudis Ferran &lt;xdrudis@tinet.cat&gt;
Reviewed-by: Kever Yang &lt;kever.yang@rock-chips.com&gt;
Tested-by: Michal Suchánek &lt;msuchanek@suse.de&gt;
</content>
</entry>
<entry>
<title>ram: rk3399: Fix faulty frequency change reports</title>
<updated>2022-09-04T12:00:38Z</updated>
<author>
<name>Lee Jones</name>
<email>lee@kernel.org</email>
</author>
<published>2022-08-11T07:58:47Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=daef678cffb9fb387c44d45d827d2b8ea199eb5b'/>
<id>urn:sha1:daef678cffb9fb387c44d45d827d2b8ea199eb5b</id>
<content type='text'>
Frequency changes to 400MHz are presently reported as:

  lpddr4_set_rate_0: change freq to 400000000 mhz 0, 1

This is obviously wrong by 6 orders of magnitude.

Ensure frequency changes are reported accurately.

Signed-off-by: Lee Jones &lt;lee@kernel.org&gt;
Tested-by: Xavier Drudis Ferran &lt;xdrudis@tinet.cat&gt;
Reviewed-by: Kever Yang &lt;kever.yang@rock-chips.com&gt;
</content>
</entry>
<entry>
<title>ram: rk3399: Fix .set_rate_index() error handling</title>
<updated>2022-09-04T12:00:38Z</updated>
<author>
<name>Lee Jones</name>
<email>lee@kernel.org</email>
</author>
<published>2022-08-11T07:58:46Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=7b561e2ab8ac980023c5e5325f45a8ca1951c0dd'/>
<id>urn:sha1:7b561e2ab8ac980023c5e5325f45a8ca1951c0dd</id>
<content type='text'>
Functions pointed to by this op pointer can return non-zero values
indicating an error.  Ensure any error value is propagated back up the
call-chain.

Signed-off-by: Lee Jones &lt;lee@kernel.org&gt;
Tested-by: Xavier Drudis Ferran &lt;xdrudis@tinet.cat&gt;
Reviewed-by: Kever Yang &lt;kever.yang@rock-chips.com&gt;
</content>
</entry>
<entry>
<title>drivers: ram: rockchip: Fix dram channels calculation for rk3399</title>
<updated>2022-09-04T12:00:38Z</updated>
<author>
<name>Han Pengfei</name>
<email>pengphei@foxmail.com</email>
</author>
<published>2022-05-15T06:11:59Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=fc1526f651a557ddbf7c3cba8575be963573871f'/>
<id>urn:sha1:fc1526f651a557ddbf7c3cba8575be963573871f</id>
<content type='text'>
Only add the dram channel when we finally setup it successfully at the
last step.

Signed-off-by: Han Pengfei &lt;pengphei@foxmail.com&gt;
Reviewed-by: Kever Yang &lt;kever.yang@rock-chips.com&gt;
</content>
</entry>
<entry>
<title>Merge tag 'tpm-03092022' of https://source.denx.de/u-boot/custodians/u-boot-tpm</title>
<updated>2022-09-03T18:55:37Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2022-09-03T18:55:37Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=427aa3c9b72b6672f714389a6f71b6cc2841d559'/>
<id>urn:sha1:427aa3c9b72b6672f714389a6f71b6cc2841d559</id>
<content type='text'>
TPM fixes and state reporting
</content>
</entry>
<entry>
<title>Merge https://source.denx.de/u-boot/custodians/u-boot-sh</title>
<updated>2022-09-03T18:55:24Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2022-09-03T18:55:24Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=bc5d11316be3cdf09c6d854070c67ec0952528ee'/>
<id>urn:sha1:bc5d11316be3cdf09c6d854070c67ec0952528ee</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tpm: Implement state command for Cr50</title>
<updated>2022-09-03T13:59:05Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2022-08-31T03:05:37Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=4c57ec76b7254cf1743748b70239bddf6100237a'/>
<id>urn:sha1:4c57ec76b7254cf1743748b70239bddf6100237a</id>
<content type='text'>
Add a vendor-specific TPM2 command for this and implement it for Cr50.
Note: This is not part of the TPM spec, but is a Cr50 extension.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Ilias Apalodimas &lt;ilias.apalodimas@linaro.org&gt;
Signed-off-by: Ilias Apalodimas &lt;ilias.apalodimas@linaro.org&gt;
</content>
</entry>
<entry>
<title>tpm: Allow reporting the internal state</title>
<updated>2022-09-03T13:59:05Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2022-08-31T03:05:36Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=3bb4db4c3883c66ee0bbf152e9ba1d2504fa8c9f'/>
<id>urn:sha1:3bb4db4c3883c66ee0bbf152e9ba1d2504fa8c9f</id>
<content type='text'>
It is useful to read information about the current TPM state, where
supported, e.g. for debugging purposes when verified boot fails.

Add support for this to the TPM interface as well as Cr50. Add a simple
sandbox test.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Ilias Apalodimas &lt;ilias.apalodimas@linaro.org&gt;
Signed-off-by: Ilias Apalodimas &lt;ilias.apalodimas@linaro.org&gt;
</content>
</entry>
</feed>
