€•«^Œsphinx.addnodes”Œdocument”“”)”}”(Œ rawsource”Œ”Œchildren”]”(Œ translations”Œ LanguagesNode”“”)”}”(hhh]”(hŒ pending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”(hhŒparent”hubaŒ attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ refdomain”Œstd”Œreftype”Œdoc”Œ reftarget”Œ0/translations/zh_CN/driver-api/men-chameleon-bus”Œmodname”NŒ classname”NŒ refexplicit”ˆuŒtagname”hhh ubh)”}”(hhh]”hŒChinese (Traditional)”…””}”(hhhh2ubah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ0/translations/zh_TW/driver-api/men-chameleon-bus”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒItalian”…””}”(hhhhFubah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ0/translations/it_IT/driver-api/men-chameleon-bus”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒJapanese”…””}”(hhhhZubah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ0/translations/ja_JP/driver-api/men-chameleon-bus”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒKorean”…””}”(hhhhnubah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ0/translations/ko_KR/driver-api/men-chameleon-bus”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒSpanish”…””}”(hhhh‚ubah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ0/translations/sp_SP/driver-api/men-chameleon-bus”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h hhŒ _document”hŒsource”NŒline”NubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒMEN Chameleon Bus”h]”hŒMEN Chameleon Bus”…””}”(hhªhh¨hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh£hžhhŸŒJ/var/lib/git/docbuild/linux/Documentation/driver-api/men-chameleon-bus.rst”h KubhŒcomment”“”)”}”(hX’Table of Contents ================= 1 Introduction 1.1 Scope of this Document 1.2 Limitations of the current implementation 2 Architecture 2.1 MEN Chameleon Bus 2.2 Carrier Devices 2.3 Parser 3 Resource handling 3.1 Memory Resources 3.2 IRQs 4 Writing an MCB driver 4.1 The driver structure 4.2 Probing and attaching 4.3 Initializing the driver 4.4 Using DMA”h]”hX’Table of Contents ================= 1 Introduction 1.1 Scope of this Document 1.2 Limitations of the current implementation 2 Architecture 2.1 MEN Chameleon Bus 2.2 Carrier Devices 2.3 Parser 3 Resource handling 3.1 Memory Resources 3.2 IRQs 4 Writing an MCB driver 4.1 The driver structure 4.2 Probing and attaching 4.3 Initializing the driver 4.4 Using DMA”…””}”(hhhh¹ubah}”(h]”h ]”h"]”h$]”h&]”Œ xml:space”Œpreserve”uh1h·hh£hžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒ Introduction”h]”hŒ Introduction”…””}”(hhÎhhÌhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hhÉhžhhŸh¶h KubhŒ paragraph”“”)”}”(hŒ{This document describes the architecture and implementation of the MEN Chameleon Bus (called MCB throughout this document).”h]”hŒ{This document describes the architecture and implementation of the MEN Chameleon Bus (called MCB throughout this document).”…””}”(hhÞhhÜhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh¶h KhhÉhžhubh¢)”}”(hhh]”(h§)”}”(hŒScope of this Document”h]”hŒScope of this Document”…””}”(hhïhhíhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hhêhžhhŸh¶h KubhÛ)”}”(hŒThis document is intended to be a short overview of the current implementation and does by no means describe the complete possibilities of MCB based devices.”h]”hŒThis document is intended to be a short overview of the current implementation and does by no means describe the complete possibilities of MCB based devices.”…””}”(hhýhhûhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh¶h K!hhêhžhubeh}”(h]”Œscope-of-this-document”ah ]”h"]”Œscope of this document”ah$]”h&]”uh1h¡hhÉhžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒ)Limitations of the current implementation”h]”hŒ)Limitations of the current implementation”…””}”(hjhjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjhžhhŸh¶h K&ubhÛ)”}”(hŒ¦The current implementation is limited to PCI and PCIe based carrier devices that only use a single memory resource and share the PCI legacy IRQ. Not implemented are:”h]”hŒ¦The current implementation is limited to PCI and PCIe based carrier devices that only use a single memory resource and share the PCI legacy IRQ. Not implemented are:”…””}”(hj$hj"hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh¶h K(hjhžhubhŒ bullet_list”“”)”}”(hhh]”(hŒ list_item”“”)”}”(hŒGMulti-resource MCB devices like the VME Controller or M-Module carrier.”h]”hÛ)”}”(hj9h]”hŒGMulti-resource MCB devices like the VME Controller or M-Module carrier.”…””}”(hj9hj;hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh¶h K,hj7ubah}”(h]”h ]”h"]”h$]”h&]”uh1j5hj2hžhhŸh¶h Nubj6)”}”(hŒƒMCB devices that need another MCB device, like SRAM for a DMA Controller's buffer descriptors or a video controller's video memory.”h]”hÛ)”}”(hŒƒMCB devices that need another MCB device, like SRAM for a DMA Controller's buffer descriptors or a video controller's video memory.”h]”hŒ‡MCB devices that need another MCB device, like SRAM for a DMA Controller’s buffer descriptors or a video controller’s video memory.”…””}”(hjThjRhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh¶h K-hjNubah}”(h]”h ]”h"]”h$]”h&]”uh1j5hj2hžhhŸh¶h Nubj6)”}”(hŒA per-carrier IRQ domain for carrier devices that have one (or more) IRQs per MCB device like PCIe based carriers with MSI or MSI-X support. ”h]”hÛ)”}”(hŒŒA per-carrier IRQ domain for carrier devices that have one (or more) IRQs per MCB device like PCIe based carriers with MSI or MSI-X support.”h]”hŒŒA per-carrier IRQ domain for carrier devices that have one (or more) IRQs per MCB device like PCIe based carriers with MSI or MSI-X support.”…””}”(hjlhjjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh¶h K/hjfubah}”(h]”h ]”h"]”h$]”h&]”uh1j5hj2hžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1j0hŸh¶h K,hjhžhubeh}”(h]”Œ)limitations-of-the-current-implementation”ah ]”h"]”Œ)limitations of the current implementation”ah$]”h&]”uh1h¡hhÉhžhhŸh¶h K&ubeh}”(h]”Œ introduction”ah ]”h"]”Œ introduction”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒ Architecture”h]”hŒ Architecture”…””}”(hj›hj™hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj–hžhhŸh¶h K3ubhÛ)”}”(hŒ(MCB is divided into 3 functional blocks:”h]”hŒ(MCB is divided into 3 functional blocks:”…””}”(hj©hj§hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh¶h K5hj–hžhubj1)”}”(hhh]”(j6)”}”(hŒThe MEN Chameleon Bus itself,”h]”hÛ)”}”(hjºh]”hŒThe MEN Chameleon Bus itself,”…””}”(hjºhj¼hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh¶h K7hj¸ubah}”(h]”h ]”h"]”h$]”h&]”uh1j5hjµhžhhŸh¶h Nubj6)”}”(hŒ#drivers for MCB Carrier Devices and”h]”hÛ)”}”(hjÑh]”hŒ#drivers for MCB Carrier Devices and”…””}”(hjÑhjÓhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh¶h K8hjÏubah}”(h]”h ]”h"]”h$]”h&]”uh1j5hjµhžhhŸh¶h Nubj6)”}”(hŒ$the parser for the Chameleon table. ”h]”hÛ)”}”(hŒ#the parser for the Chameleon table.”h]”hŒ#the parser for the Chameleon table.”…””}”(hjìhjêhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh¶h K9hjæubah}”(h]”h ]”h"]”h$]”h&]”uh1j5hjµhžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”j„j…uh1j0hŸh¶h K7hj–hžhubh¢)”}”(hhh]”(h§)”}”(hŒMEN Chameleon Bus”h]”hŒMEN Chameleon Bus”…””}”(hj hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjhžhhŸh¶h Khjhžhubeh}”(h]”Œid1”ah ]”h"]”h$]”Œmen chameleon bus”ah&]”uh1h¡hj–hžhhŸh¶h K<Œ referenced”Kubh¢)”}”(hhh]”(h§)”}”(hŒCarrier Devices”h]”hŒCarrier Devices”…””}”(hj1hj/hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj,hžhhŸh¶h KHubhÛ)”}”(hX:A carrier device is just an abstraction for the real world physical bus the Chameleon FPGA is attached to. Some IP Core drivers may need to interact with properties of the carrier device (like querying the IRQ number of a PCI device). To provide abstraction from the real hardware bus, an MCB carrier device provides callback methods to translate the driver's MCB function calls to hardware related function calls. For example a carrier device may implement the get_irq() method which can be translated into a hardware bus query for the IRQ number the device should use.”h]”hX<A carrier device is just an abstraction for the real world physical bus the Chameleon FPGA is attached to. Some IP Core drivers may need to interact with properties of the carrier device (like querying the IRQ number of a PCI device). To provide abstraction from the real hardware bus, an MCB carrier device provides callback methods to translate the driver’s MCB function calls to hardware related function calls. For example a carrier device may implement the get_irq() method which can be translated into a hardware bus query for the IRQ number the device should use.”…””}”(hj?hj=hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh¶h KJhj,hžhubeh}”(h]”Œcarrier-devices”ah ]”h"]”Œcarrier devices”ah$]”h&]”uh1h¡hj–hžhhŸh¶h KHubh¢)”}”(hhh]”(h§)”}”(hŒParser”h]”hŒParser”…””}”(hjXhjVhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjShžhhŸh¶h KTubhÛ)”}”(hXThe parser reads the first 512 bytes of a Chameleon device and parses the Chameleon table. Currently the parser only supports the Chameleon v2 variant of the Chameleon table but can easily be adopted to support an older or possible future variant. While parsing the table's entries new MCB devices are allocated and their resources are assigned according to the resource assignment in the Chameleon table. After resource assignment is finished, the MCB devices are registered at the MCB and thus at the driver core of the Linux kernel.”h]”hXThe parser reads the first 512 bytes of a Chameleon device and parses the Chameleon table. Currently the parser only supports the Chameleon v2 variant of the Chameleon table but can easily be adopted to support an older or possible future variant. While parsing the table’s entries new MCB devices are allocated and their resources are assigned according to the resource assignment in the Chameleon table. After resource assignment is finished, the MCB devices are registered at the MCB and thus at the driver core of the Linux kernel.”…””}”(hjfhjdhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh¶h KVhjShžhubeh}”(h]”Œparser”ah ]”h"]”Œparser”ah$]”h&]”uh1h¡hj–hžhhŸh¶h KTubeh}”(h]”Œ architecture”ah ]”h"]”Œ architecture”ah$]”h&]”uh1h¡hh£hžhhŸh¶h K3ubh¢)”}”(hhh]”(h§)”}”(hŒResource handling”h]”hŒResource handling”…””}”(hj‡hj…hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj‚hžhhŸh¶h K`ubhÛ)”}”(hŒŒThe current implementation assigns exactly one memory and one IRQ resource per MCB device. But this is likely going to change in the future.”h]”hŒŒThe current implementation assigns exactly one memory and one IRQ resource per MCB device. But this is likely going to change in the future.”…””}”(hj•hj“hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh¶h Kbhj‚hžhubh¢)”}”(hhh]”(h§)”}”(hŒMemory Resources”h]”hŒMemory Resources”…””}”(hj¦hj¤hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj¡hžhhŸh¶h KfubhÛ)”}”(hX+Each MCB device has exactly one memory resource, which can be requested from the MCB bus. This memory resource is the physical address of the MCB device inside the carrier and is intended to be passed to ioremap() and friends. It is already requested from the kernel by calling request_mem_region().”h]”hX+Each MCB device has exactly one memory resource, which can be requested from the MCB bus. This memory resource is the physical address of the MCB device inside the carrier and is intended to be passed to ioremap() and friends. It is already requested from the kernel by calling request_mem_region().”…””}”(hj´hj²hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh¶h Khhj¡hžhubeh}”(h]”Œmemory-resources”ah ]”h"]”Œmemory resources”ah$]”h&]”uh1h¡hj‚hžhhŸh¶h Kfubh¢)”}”(hhh]”(h§)”}”(hŒIRQs”h]”hŒIRQs”…””}”(hjÍhjËhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjÈhžhhŸh¶h KnubhÛ)”}”(hXZEach MCB device has exactly one IRQ resource, which can be requested from the MCB bus. If a carrier device driver implements the ->get_irq() callback method, the IRQ number assigned by the carrier device will be returned, otherwise the IRQ number inside the Chameleon table will be returned. This number is suitable to be passed to request_irq().”h]”hXZEach MCB device has exactly one IRQ resource, which can be requested from the MCB bus. If a carrier device driver implements the ->get_irq() callback method, the IRQ number assigned by the carrier device will be returned, otherwise the IRQ number inside the Chameleon table will be returned. This number is suitable to be passed to request_irq().”…””}”(hjÛhjÙhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh¶h KphjÈhžhubeh}”(h]”Œirqs”ah ]”h"]”Œirqs”ah$]”h&]”uh1h¡hj‚hžhhŸh¶h Knubeh}”(h]”Œresource-handling”ah ]”h"]”Œresource handling”ah$]”h&]”uh1h¡hh£hžhhŸh¶h K`ubh¢)”}”(hhh]”(h§)”}”(hŒWriting an MCB driver”h]”hŒWriting an MCB driver”…””}”(hjühjúhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj÷hžhhŸh¶h Kwubh¢)”}”(hhh]”(h§)”}”(hŒThe driver structure”h]”hŒThe driver structure”…””}”(hj hj hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjhžhhŸh¶h KzubhÛ)”}”(hŒôEach MCB driver has a structure to identify the device driver as well as device ids which identify the IP Core inside the FPGA. The driver structure also contains callback methods which get executed on driver probe and removal from the system::”h]”hŒóEach MCB driver has a structure to identify the device driver as well as device ids which identify the IP Core inside the FPGA. The driver structure also contains callback methods which get executed on driver probe and removal from the system:”…””}”(hŒóEach MCB driver has a structure to identify the device driver as well as device ids which identify the IP Core inside the FPGA. The driver structure also contains callback methods which get executed on driver probe and removal from the system:”hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh¶h K|hjhžhubhŒ literal_block”“”)”}”(hXHstatic const struct mcb_device_id foo_ids[] = { { .device = 0x123 }, { } }; MODULE_DEVICE_TABLE(mcb, foo_ids); static struct mcb_driver foo_driver = { driver = { .name = "foo-bar", .owner = THIS_MODULE, }, .probe = foo_probe, .remove = foo_remove, .id_table = foo_ids, };”h]”hXHstatic const struct mcb_device_id foo_ids[] = { { .device = 0x123 }, { } }; MODULE_DEVICE_TABLE(mcb, foo_ids); static struct mcb_driver foo_driver = { driver = { .name = "foo-bar", .owner = THIS_MODULE, }, .probe = foo_probe, .remove = foo_remove, .id_table = foo_ids, };”…””}”(hhhj*ubah}”(h]”h ]”h"]”h$]”h&]”hÇhÈuh1j(hŸh¶h Khjhžhubeh}”(h]”Œthe-driver-structure”ah ]”h"]”Œthe driver structure”ah$]”h&]”uh1h¡hj÷hžhhŸh¶h Kzubh¢)”}”(hhh]”(h§)”}”(hŒProbing and attaching”h]”hŒProbing and attaching”…””}”(hjEhjChžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj@hžhhŸh¶h K’ubhÛ)”}”(hŒæWhen a driver is loaded and the MCB devices it services are found, the MCB core will call the driver's probe callback method. When the driver is removed from the system, the MCB core will call the driver's remove callback method::”h]”hŒéWhen a driver is loaded and the MCB devices it services are found, the MCB core will call the driver’s probe callback method. When the driver is removed from the system, the MCB core will call the driver’s remove callback method:”…””}”(hŒåWhen a driver is loaded and the MCB devices it services are found, the MCB core will call the driver's probe callback method. When the driver is removed from the system, the MCB core will call the driver's remove callback method:”hjQhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh¶h K”hj@hžhubj))”}”(hŒ€static init foo_probe(struct mcb_device *mdev, const struct mcb_device_id *id); static void foo_remove(struct mcb_device *mdev);”h]”hŒ€static init foo_probe(struct mcb_device *mdev, const struct mcb_device_id *id); static void foo_remove(struct mcb_device *mdev);”…””}”(hhhj`ubah}”(h]”h ]”h"]”h$]”h&]”hÇhÈuh1j(hŸh¶h K˜hj@hžhubeh}”(h]”Œprobing-and-attaching”ah ]”h"]”Œprobing and attaching”ah$]”h&]”uh1h¡hj÷hžhhŸh¶h K’ubh¢)”}”(hhh]”(h§)”}”(hŒInitializing the driver”h]”hŒInitializing the driver”…””}”(hj{hjyhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjvhžhhŸh¶h KœubhÛ)”}”(hŒ±When the kernel is booted or your foo driver module is inserted, you have to perform driver initialization. Usually it is enough to register your driver module at the MCB core::”h]”hŒ°When the kernel is booted or your foo driver module is inserted, you have to perform driver initialization. Usually it is enough to register your driver module at the MCB core:”…””}”(hŒ°When the kernel is booted or your foo driver module is inserted, you have to perform driver initialization. Usually it is enough to register your driver module at the MCB core:”hj‡hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh¶h Kžhjvhžhubj))”}”(hŒÖstatic int __init foo_init(void) { return mcb_register_driver(&foo_driver); } module_init(foo_init); static void __exit foo_exit(void) { mcb_unregister_driver(&foo_driver); } module_exit(foo_exit);”h]”hŒÖstatic int __init foo_init(void) { return mcb_register_driver(&foo_driver); } module_init(foo_init); static void __exit foo_exit(void) { mcb_unregister_driver(&foo_driver); } module_exit(foo_exit);”…””}”(hhhj–ubah}”(h]”h ]”h"]”h$]”h&]”hÇhÈuh1j(hŸh¶h K¢hjvhžhubhÛ)”}”(hŒDThe module_mcb_driver() macro can be used to reduce the above code::”h]”hŒCThe module_mcb_driver() macro can be used to reduce the above code:”…””}”(hŒCThe module_mcb_driver() macro can be used to reduce the above code:”hj¤hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh¶h K®hjvhžhubj))”}”(hŒmodule_mcb_driver(foo_driver);”h]”hŒmodule_mcb_driver(foo_driver);”…””}”(hhhj³ubah}”(h]”h ]”h"]”h$]”h&]”hÇhÈuh1j(hŸh¶h K°hjvhžhubeh}”(h]”Œinitializing-the-driver”ah ]”h"]”Œinitializing the driver”ah$]”h&]”uh1h¡hj÷hžhhŸh¶h Kœubh¢)”}”(hhh]”(h§)”}”(hŒ Using DMA”h]”hŒ Using DMA”…””}”(hjÎhjÌhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjÉhžhhŸh¶h K³ubhÛ)”}”(hŒÒTo make use of the kernel's DMA-API's function, you will need to use the carrier device's 'struct device'. Fortunately 'struct mcb_device' embeds a pointer (->dma_dev) to the carrier's device for DMA purposes::”h]”hŒáTo make use of the kernel’s DMA-API’s function, you will need to use the carrier device’s ‘struct device’. Fortunately ‘struct mcb_device’ embeds a pointer (->dma_dev) to the carrier’s device for DMA purposes:”…””}”(hŒÑTo make use of the kernel's DMA-API's function, you will need to use the carrier device's 'struct device'. Fortunately 'struct mcb_device' embeds a pointer (->dma_dev) to the carrier's device for DMA purposes:”hjÚhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh¶h KµhjÉhžhubj))”}”(hŒlret = dma_set_mask_and_coherent(&mdev->dma_dev, DMA_BIT_MASK(dma_bits)); if (rc) /* Handle errors */”h]”hŒlret = dma_set_mask_and_coherent(&mdev->dma_dev, DMA_BIT_MASK(dma_bits)); if (rc) /* Handle errors */”…””}”(hhhjéubah}”(h]”h ]”h"]”h$]”h&]”hÇhÈuh1j(hŸh¶h K¹hjÉhžhubeh}”(h]”Œ using-dma”ah ]”h"]”Œ using dma”ah$]”h&]”uh1h¡hj÷hžhhŸh¶h K³ubeh}”(h]”Œwriting-an-mcb-driver”ah ]”h"]”Œwriting an mcb driver”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kwubeh}”(h]”Œmen-chameleon-bus”ah ]”h"]”h$]”j)ah&]”uh1h¡hhhžhhŸh¶h Kj+Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h¶uh1hŒcurrent_source”NŒ current_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¦NŒ generator”NŒ datestamp”NŒ source_link”NŒ source_url”NŒ toc_backlinks”Œentry”Œfootnote_backlinks”KŒ sectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒ strip_classes”NŒ report_level”KŒ halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ traceback”ˆŒinput_encoding”Œ utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”j1Œerror_encoding”ŒUTF-8”Œerror_encoding_error_handler”Œbackslashreplace”Œ language_code”Œen”Œrecord_dependencies”NŒconfig”NŒ id_prefix”hŒauto_id_prefix”Œid”Œ dump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h¶Œ _destination”NŒ _config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒpep_references”NŒ pep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒ rfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ tab_width”KŒtrim_footnote_reference_space”‰Œfile_insertion_enabled”ˆŒ raw_enabled”KŒline_length_limit”M'Œsyntax_highlight”Œlong”Œ smart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œ docinfo_xform”KŒsectsubtitle_xform”‰Œ image_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œ embed_images”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(Œmen chameleon bus”Nj“jjj j‹jˆjj|jPjMjwjtjôjñjÅjÂjìjéjjj=j:jsjpjÆjÃjüjùuŒ nametypes”}”(jvNj“NjNj‹NjNjPNjwNjôNjÅNjìNjNj=NjsNjÆNjüNuh}”(j h£jhÉj hêjˆjj|j–j%jjMj,jtjSjñj‚jÂj¡jéjÈjj÷j:jjpj@jÃjvjùjÉuŒ footnote_refs”}”Œ citation_refs”}”Œ autofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ footnotes”]”Œ citations”]”Œautofootnote_start”KŒsymbol_footnote_start”KŒ id_counter”Œ collections”ŒCounter”“”}”j?Ks…”R”Œparse_messages”]”hŒsystem_message”“”)”}”(hhh]”hÛ)”}”(hŒ4Duplicate implicit target name: "men chameleon bus".”h]”hŒ8Duplicate implicit target name: “men chameleon busâ€.”…””}”(hhhjšhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhj—ubah}”(h]”h ]”h"]”h$]”h&]”j%aŒlevel”KŒtype”ŒINFO”Œsource”h¶Œline”K