From WikiChip
Editing intel/microarchitectures/ice lake (client)

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

This page supports semantic in-text annotations (e.g. "[[Is specified as::World Heritage Site]]") to build structured and queryable content provided by Semantic MediaWiki. For a comprehensive description on how to use annotations or the #ask parser function, please have a look at the getting started, in-text annotation, or inline queries help pages.

Latest revision Your text
Line 239: Line 239:
  
  
Previously (e.g., with {{\\|Whiskey Lake}}), for OEMs to support Thunderbolt 3 in mobile devices, they had to use Intel's Titan Ridge controller. Titan Ridge was a discrete Thunderbolt 3 chip that came with either one or two dedicated [[Thunderbolt 3]] ports. In order to support everything that was necessary (e.g., legacy [[USB 2]] as well as high speed PCIe Gen 3), the controller was connected to both the CPU and the chipset. The chipset was connected over four PCIe Gen 3 lanes. The CPU had two DisplayPort connections. Each of those passed over four PCIe Gen 3 lanes. In order to offer legacy I/O support, a direct USB 2.0 link from the PCH went to the port. For charging capabilities, the port was also connected directly to a Power Deliver (PD) controller. In total, 17 PCIe Gen 3 lanes operating at around 8 GT/s were required between the Titan Ridge controller and the chipset and CPU.
+
Previously (e.g., with {{\\|Whiskey Lake}}), for OEMs to support Thunderbolt 3 in mobile devices, they had to use Intel's Titan Ridge controller. Titan Ridge was a discrete Thunderbolt 3 chip that came with either one or two dedicated [[Thunderbolt 3]] ports. In order to support everything that was necessary (e.g., legacy [[USB 2]] as well as high speed PCIe Gen 3), the controller was connected to both the CPU and the hipset. The chipset was connected over four PCIe Gen 3 lanes. The CPU had two DisplayPort connections. Each of those passed over four PCIe Gen 3 lanes. In order to offer legacy I/O support, a direct USB 2.0 link from the PCH went to the port. For charging capabilities, the port was also connected directly to a Power Deliver (PD) controller. In total, 17 PCIe Gen 3 lanes operating at around 8 GT/s were required between the Titan Ridge controller and the chipset and CPU.
  
 
Due to the design complexity introduced by the discrete controller, most mobile devices that made use of Titan Ridge only supported it on one side of the device - typically on the side of the device closer to the controller itself.
 
Due to the design complexity introduced by the discrete controller, most mobile devices that made use of Titan Ridge only supported it on one side of the device - typically on the side of the device closer to the controller itself.

Please note that all contributions to WikiChip may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see WikiChip:Copyrights for details). Do not submit copyrighted work without permission!

Cancel | Editing help (opens in new window)

This page is a member of 1 hidden category:

codenameIce Lake (client) +
core count2 + and 4 +
designerIntel +
first launchedMay 27, 2019 +
full page nameintel/microarchitectures/ice lake (client) +
instance ofmicroarchitecture +
instruction set architecturex86-64 +
manufacturerIntel +
microarchitecture typeCPU +
nameIce Lake (client) +
pipeline stages (max)19 +
pipeline stages (min)14 +
process10 nm (0.01 μm, 1.0e-5 mm) +