<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rt-thread.git/components/drivers/core, branch v5.2.0-beta</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/rt-thread.git/atom/components/drivers/core?h=v5.2.0-beta</id>
<link rel='self' href='http://cgit.235523.xyz/rt-thread.git/atom/components/drivers/core?h=v5.2.0-beta'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/rt-thread.git/'/>
<updated>2025-03-19T03:43:00Z</updated>
<entry>
<title>[DM/Platform] Fixup the node will probe more than once</title>
<updated>2025-03-19T03:43:00Z</updated>
<author>
<name>GUI</name>
<email>39894654+GuEe-GUI@users.noreply.github.com</email>
</author>
<published>2025-03-18T04:28:04Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/rt-thread.git/commit/?id=39f5df440e8abd8dacab7b602baa9896ad478953'/>
<id>urn:sha1:39f5df440e8abd8dacab7b602baa9896ad478953</id>
<content type='text'>
If a node request a new node or it's parent node. the  request's node will probe a double time.
So we check the device object of node in ofw probe entry and ofw probe child exit.</content>
</entry>
<entry>
<title>[DM] Replace spinlock static init by RT_DEFINE_SPINLOCK</title>
<updated>2025-02-11T06:58:18Z</updated>
<author>
<name>GuEe-GUI</name>
<email>2991707448@qq.com</email>
</author>
<published>2025-02-10T06:19:30Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/rt-thread.git/commit/?id=f50607628192b7ad1828e811bba238993b9afd55'/>
<id>urn:sha1:f50607628192b7ad1828e811bba238993b9afd55</id>
<content type='text'>
Signed-off-by: GuEe-GUI &lt;2991707448@qq.com&gt;
</content>
</entry>
<entry>
<title>修复编译过程中的 DFS_V2报错、FAL警告</title>
<updated>2025-01-02T00:02:50Z</updated>
<author>
<name>yuqingli05</name>
<email>106426122+yuqingli05@users.noreply.github.com</email>
</author>
<published>2025-01-02T00:02:50Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/rt-thread.git/commit/?id=d57b7cb40af7e41624eb7b31fc38446921a975bf'/>
<id>urn:sha1:d57b7cb40af7e41624eb7b31fc38446921a975bf</id>
<content type='text'>
</content>
</entry>
<entry>
<title>[DM/FEATURE] Support clock subprobe in OFW</title>
<updated>2024-11-18T07:03:23Z</updated>
<author>
<name>GuEe-GUI</name>
<email>2991707448@qq.com</email>
</author>
<published>2024-10-24T04:00:15Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/rt-thread.git/commit/?id=6185250c86af49ca12ca923c8fd3e70b37143310'/>
<id>urn:sha1:6185250c86af49ca12ca923c8fd3e70b37143310</id>
<content type='text'>
Signed-off-by: GuEe-GUI &lt;2991707448@qq.com&gt;
</content>
</entry>
<entry>
<title>[DM/FEATURE] Support driver depends fix auto</title>
<updated>2024-11-18T07:03:23Z</updated>
<author>
<name>GuEe-GUI</name>
<email>2991707448@qq.com</email>
</author>
<published>2024-10-24T03:56:31Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/rt-thread.git/commit/?id=cefe6d63805b89fb96aea69eb8e14fa12260192a'/>
<id>urn:sha1:cefe6d63805b89fb96aea69eb8e14fa12260192a</id>
<content type='text'>
We need a API to fix the driver load auto when
a second driver get it in probe process that
we can not be careful of the driver-to-driver's
depends in different SoC.

Signed-off-by: GuEe-GUI &lt;2991707448@qq.com&gt;
</content>
</entry>
<entry>
<title>[DM/FIXUP] remove OFW switch macros</title>
<updated>2024-11-18T07:03:23Z</updated>
<author>
<name>GuEe-GUI</name>
<email>2991707448@qq.com</email>
</author>
<published>2024-10-24T03:52:36Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/rt-thread.git/commit/?id=b6f67285e942737fdddae7dae5acaa2045c1bead'/>
<id>urn:sha1:b6f67285e942737fdddae7dae5acaa2045c1bead</id>
<content type='text'>
The drivers will support OFW and name probe both.
We should make build OK when OFW is disable.

Signed-off-by: GuEe-GUI &lt;2991707448@qq.com&gt;
</content>
</entry>
<entry>
<title>[DM/FEATURE] DM Device IDA management</title>
<updated>2024-11-18T06:23:25Z</updated>
<author>
<name>GuEe-GUI</name>
<email>2991707448@qq.com</email>
</author>
<published>2024-10-23T11:07:06Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/rt-thread.git/commit/?id=3b22dbd04960a1934994059a4ef97d8403be2a54'/>
<id>urn:sha1:3b22dbd04960a1934994059a4ef97d8403be2a54</id>
<content type='text'>
Drivers can manage their own IDs without having to concern
themselves with the register/unregister in system

Link: https://github.com/RT-Thread/rt-thread/issues/9534

Signed-off-by: GuEe-GUI &lt;2991707448@qq.com&gt;
</content>
</entry>
<entry>
<title>[fix]:fix log format and reopen with a different oflag issue (#9452)</title>
<updated>2024-09-19T10:15:55Z</updated>
<author>
<name>milo</name>
<email>1569491816@qq.com</email>
</author>
<published>2024-09-19T10:15:55Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/rt-thread.git/commit/?id=2a8aba4c8b8c5a9f415cfa24316eba8a5573cc4a'/>
<id>urn:sha1:2a8aba4c8b8c5a9f415cfa24316eba8a5573cc4a</id>
<content type='text'>
fix log format and reopen with a different oflag issue</content>
</entry>
<entry>
<title>Fixup platform not free device in OFW</title>
<updated>2024-09-03T23:49:47Z</updated>
<author>
<name>GuEe-GUI</name>
<email>2991707448@qq.com</email>
</author>
<published>2024-07-09T09:17:00Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/rt-thread.git/commit/?id=175a2ff954a8ad6ce9a1739c8338b665b6abef80'/>
<id>urn:sha1:175a2ff954a8ad6ce9a1739c8338b665b6abef80</id>
<content type='text'>
Signed-off-by: GuEe-GUI &lt;2991707448@qq.com&gt;
</content>
</entry>
<entry>
<title>Fixup bus remove device option</title>
<updated>2024-09-03T23:49:47Z</updated>
<author>
<name>GuEe-GUI</name>
<email>2991707448@qq.com</email>
</author>
<published>2024-07-09T09:15:02Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/rt-thread.git/commit/?id=2ec69c3ce43f123748c52140c40ad24e6d4b3b10'/>
<id>urn:sha1:2ec69c3ce43f123748c52140c40ad24e6d4b3b10</id>
<content type='text'>
The bus should call driver's `remove` callback not
instead of `shutdown` in rt_bus_remove_device.

Signed-off-by: GuEe-GUI &lt;2991707448@qq.com&gt;
</content>
</entry>
</feed>
