€•è/      Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ0/translations/zh_CN/admin-guide/gpio/gpio-mockup”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ0/translations/zh_TW/admin-guide/gpio/gpio-mockup”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ0/translations/it_IT/admin-guide/gpio/gpio-mockup”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ0/translations/ja_JP/admin-guide/gpio/gpio-mockup”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ0/translations/ko_KR/admin-guide/gpio/gpio-mockup”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ0/translations/sp_SP/admin-guide/gpio/gpio-mockup”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒcomment”“”)”}”(hŒ%SPDX-License-Identifier: GPL-2.0-only”h]”hŒ%SPDX-License-Identifier: GPL-2.0-only”…””}”hh£sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1h¡hhhžhhŸŒJ/var/lib/git/docbuild/linux/Documentation/admin-guide/gpio/gpio-mockup.rst”h KubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒGPIO Testing Driver”h]”hŒGPIO Testing Driver”…””}”(hh»hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hh¶hžhhŸh³h KubhŒnote”“”)”}”(hŒýThis module has been obsoleted by the more flexible gpio-sim.rst.
New developments should use that API and existing developments are
encouraged to migrate as soon as possible.
This module will continue to be maintained but no new features will be
added.”h]”hŒ	paragraph”“”)”}”(hŒýThis module has been obsoleted by the more flexible gpio-sim.rst.
New developments should use that API and existing developments are
encouraged to migrate as soon as possible.
This module will continue to be maintained but no new features will be
added.”h]”hŒýThis module has been obsoleted by the more flexible gpio-sim.rst.
New developments should use that API and existing developments are
encouraged to migrate as soon as possible.
This module will continue to be maintained but no new features will be
added.”…””}”(hhÑhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KhhËubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhh¶hžhhŸh³h NubhÐ)”}”(hX  The GPIO Testing Driver (gpio-mockup) provides a way to create simulated GPIO
chips for testing purposes. The lines exposed by these chips can be accessed
using the standard GPIO character device interface as well as manipulated
using the dedicated debugfs directory structure.”h]”hX  The GPIO Testing Driver (gpio-mockup) provides a way to create simulated GPIO
chips for testing purposes. The lines exposed by these chips can be accessed
using the standard GPIO character device interface as well as manipulated
using the dedicated debugfs directory structure.”…””}”(hhåhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Khh¶hžhubhµ)”}”(hhh]”(hº)”}”(hŒ,Creating simulated chips using module params”h]”hŒ,Creating simulated chips using module params”…””}”(hhöhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hhóhžhhŸh³h KubhÐ)”}”(hŒWWhen loading the gpio-mockup driver a number of parameters can be passed to the
module.”h]”hŒWWhen loading the gpio-mockup driver a number of parameters can be passed to the
module.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h KhhóhžhubhŒblock_quote”“”)”}”(hXy  gpio_mockup_ranges

    This parameter takes an argument in the form of an array of integer
    pairs. Each pair defines the base GPIO number (non-negative integer)
    and the first number after the last of this chip. If the base GPIO
    is -1, the gpiolib will assign it automatically. while the following
    parameter is the number of lines exposed by the chip.

    Example: gpio_mockup_ranges=-1,8,-1,16,405,409

    The line above creates three chips. The first one will expose 8 lines,
    the second 16 and the third 4. The base GPIO for the third chip is set
    to 405 while for two first chips it will be assigned automatically.

gpio_mockup_named_lines

    This parameter doesn't take any arguments. It lets the driver know that
    GPIO lines exposed by it should be named.

    The name format is: gpio-mockup-X-Y where X is mockup chip's ID
    and Y is the line offset.
”h]”(hÐ)”}”(hŒgpio_mockup_ranges”h]”hŒgpio_mockup_ranges”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Khj  ubj  )”}”(hXJ  This parameter takes an argument in the form of an array of integer
pairs. Each pair defines the base GPIO number (non-negative integer)
and the first number after the last of this chip. If the base GPIO
is -1, the gpiolib will assign it automatically. while the following
parameter is the number of lines exposed by the chip.

Example: gpio_mockup_ranges=-1,8,-1,16,405,409

The line above creates three chips. The first one will expose 8 lines,
the second 16 and the third 4. The base GPIO for the third chip is set
to 405 while for two first chips it will be assigned automatically.
”h]”(hÐ)”}”(hXF  This parameter takes an argument in the form of an array of integer
pairs. Each pair defines the base GPIO number (non-negative integer)
and the first number after the last of this chip. If the base GPIO
is -1, the gpiolib will assign it automatically. while the following
parameter is the number of lines exposed by the chip.”h]”hXF  This parameter takes an argument in the form of an array of integer
pairs. Each pair defines the base GPIO number (non-negative integer)
and the first number after the last of this chip. If the base GPIO
is -1, the gpiolib will assign it automatically. while the following
parameter is the number of lines exposed by the chip.”…””}”(hj*  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h Khj&  ubhÐ)”}”(hŒ.Example: gpio_mockup_ranges=-1,8,-1,16,405,409”h]”hŒ.Example: gpio_mockup_ranges=-1,8,-1,16,405,409”…””}”(hj8  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K!hj&  ubhÐ)”}”(hŒÑThe line above creates three chips. The first one will expose 8 lines,
the second 16 and the third 4. The base GPIO for the third chip is set
to 405 while for two first chips it will be assigned automatically.”h]”hŒÑThe line above creates three chips. The first one will expose 8 lines,
the second 16 and the third 4. The base GPIO for the third chip is set
to 405 while for two first chips it will be assigned automatically.”…””}”(hjF  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K#hj&  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hŸh³h Khj  ubhÐ)”}”(hŒgpio_mockup_named_lines”h]”hŒgpio_mockup_named_lines”…””}”(hjZ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K'hj  ubj  )”}”(hŒÍThis parameter doesn't take any arguments. It lets the driver know that
GPIO lines exposed by it should be named.

The name format is: gpio-mockup-X-Y where X is mockup chip's ID
and Y is the line offset.
”h]”(hÐ)”}”(hŒqThis parameter doesn't take any arguments. It lets the driver know that
GPIO lines exposed by it should be named.”h]”hŒsThis parameter doesnâ€™t take any arguments. It lets the driver know that
GPIO lines exposed by it should be named.”…””}”(hjl  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K)hjh  ubhÐ)”}”(hŒYThe name format is: gpio-mockup-X-Y where X is mockup chip's ID
and Y is the line offset.”h]”hŒ[The name format is: gpio-mockup-X-Y where X is mockup chipâ€™s ID
and Y is the line offset.”…””}”(hjz  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K,hjh  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hŸh³h K)hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hŸh³h Khhóhžhubeh}”(h]”Œ,creating-simulated-chips-using-module-params”ah ]”h"]”Œ,creating simulated chips using module params”ah$]”h&]”uh1h´hh¶hžhhŸh³h Kubhµ)”}”(hhh]”(hº)”}”(hŒManipulating simulated lines”h]”hŒManipulating simulated lines”…””}”(hjŸ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjœ  hžhhŸh³h K0ubhÐ)”}”(hŒÜEach mockup chip creates its own subdirectory in /sys/kernel/debug/gpio-mockup/.
The directory is named after the chip's label. A symlink is also created, named
after the chip's name, which points to the label directory.”h]”hŒàEach mockup chip creates its own subdirectory in /sys/kernel/debug/gpio-mockup/.
The directory is named after the chipâ€™s label. A symlink is also created, named
after the chipâ€™s name, which points to the label directory.”…””}”(hj­  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K2hjœ  hžhubhÐ)”}”(hŒŽInside each subdirectory, there's a separate attribute for each GPIO line. The
name of the attribute represents the line's offset in the chip.”h]”hŒ’Inside each subdirectory, thereâ€™s a separate attribute for each GPIO line. The
name of the attribute represents the lineâ€™s offset in the chip.”…””}”(hj»  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K6hjœ  hžhubhÐ)”}”(hŒ³Reading from a line attribute returns the current value. Writing to it (0 or 1)
changes the configuration of the simulated pull-up/pull-down resistor
(1 - pull-up, 0 - pull-down).”h]”hŒ³Reading from a line attribute returns the current value. Writing to it (0 or 1)
changes the configuration of the simulated pull-up/pull-down resistor
(1 - pull-up, 0 - pull-down).”…””}”(hjÉ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÏhŸh³h K9hjœ  hžhubeh}”(h]”Œmanipulating-simulated-lines”ah ]”h"]”Œmanipulating simulated lines”ah$]”h&]”uh1h´hh¶hžhhŸh³h K0ubeh}”(h]”Œgpio-testing-driver”ah ]”h"]”Œgpio testing driver”ah$]”h&]”uh1h´hhhžhhŸh³h 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”j
  Œ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Œfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œ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”‰Œ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”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(jä  já  j™  j–  jÜ  jÙ  uŒ	nametypes”}”(jä  ‰j™  ‰jÜ  ‰uh}”(já  h¶j–  hójÙ  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”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nhžhub.