Home
last modified time | relevance | path

Searched +full:board +full:- +full:type (Results 1 – 25 of 1097) sorted by relevance

12345678910>>...44

/openbmc/linux/drivers/nubus/
H A Dnubus.c1 // SPDX-License-Identifier: GPL-2.0
7 * Mostly rewritten by David Huggins-Daines, C. Scott Ananian,
37 * thought to be suitable for that and some board ROMs make it too expensive.
60 little-endian machine. Again, stranger things have happened)
88 len--; in nubus_get_rom()
100 p--; in nubus_rewind()
102 len--; in nubus_rewind()
115 len--; in nubus_advance()
127 nubus_rewind(ptr, -len, map); in nubus_move()
135 /* Each sResource entry consists of a 1-byte ID and a 3-byte data
[all …]
/openbmc/linux/drivers/media/common/siano/
H A Dsms-cards.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * Card-specific functions for the Siano SMS1xxx USB dongle
8 #include "sms-cards.h"
14 .name = "Unknown board",
15 .type = SMS_UNKNOWN_TYPE,
20 .type = SMS_STELLAR,
25 .type = SMS_NOVA_A0,
30 .type = SMS_NOVA_B0,
35 .type = SMS_VEGA,
40 .type = SMS_STELLAR,
[all …]
/openbmc/u-boot/arch/arm/mach-rockchip/rk3399/
H A DKconfig4 prompt "RK3399 board select"
7 bool "RK3399 evaluation board"
9 RK3399evb is a evaluation board for Rockchp rk3399,
10 with full function and phisical connectors support like type-C ports,
11 usb2.0 host ports, LVDS, JTAG, MAC, SDcard, HDMI, USB-2-serial...
14 bool "Theobroma Systems RK3399-Q7 (Puma)"
16 The RK3399-Q7 (Puma) is a system-on-module (designed and
18 in a Qseven-compatible form-factor (running of a single 5V
19 supply and exposing its external interfaces on a MXM-230
22 Key features of the RK3399-Q7 include:
[all …]
/openbmc/openbmc/meta-facebook/meta-bletchley/recipes-bletchley/board-type-checker/
H A Dboard-type-checker.bb1 SUMMARY = "Bletchley board type checker"
2 DESCRIPTION = "Bletchley board type checker to probe i2c device with correct driver in user-space"
4 LICENSE = "Apache-2.0"
5 LIC_FILES_CHKSUM = "file://${COREBASE}/meta/files/common-licenses/Apache-2.0;md5=89aea4e17d99a7cacd…
7 inherit allarch systemd obmc-phosphor-systemd
12 RDEPENDS:${PN} += " bash i2c-tools"
14 SRC_URI = " file://board-type-checker-fpb \
15 file://board-type-checker-fpb.service \
19 SYSTEMD_SERVICE:${PN}:append = " board-type-checker-fpb.service"
22 install -d ${D}${libexecdir}
[all …]
/openbmc/linux/arch/mips/cavium-octeon/executive/
H A Dcvmx-helper-board.c7 * Copyright (c) 2003-2008 Cavium Networks
14 * AS-IS and WITHOUT ANY WARRANTY; without even the implied warranty
21 * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
30 * Helper functions to abstract board specific data about
31 * network ports from the rest of the cvmx-helper files.
36 #include <asm/octeon/cvmx-bootinfo.h>
38 #include <asm/octeon/cvmx-config.h>
40 #include <asm/octeon/cvmx-helper.h>
41 #include <asm/octeon/cvmx-helper-util.h>
42 #include <asm/octeon/cvmx-helper-board.h>
[all …]
/openbmc/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/dbus/fan-fault-led/
H A Dboard-0-fan-1.yaml1 - name: board 0 fan 1 current critical alarm path group
5 - meta: PATH
7 - meta: PATH
10 - name: current fan critical alarm property
13 type: boolean
15 - interface: xyz.openbmc_project.Sensor.Threshold.Critical
18 - interface: xyz.openbmc_project.Sensor.Threshold.Critical
22 - name: board 0 fan 1 critical alarm assert
25 paths: board 0 fan 1 current critical alarm path group
29 - name: board 0 fan 1 critical alarm deassert
[all …]
H A Dboard-0-fan-5.yaml1 - name: board 0 fan 5 current critical alarm path group
5 - meta: PATH
7 - meta: PATH
10 - name: current fan critical alarm property
13 type: boolean
15 - interface: xyz.openbmc_project.Sensor.Threshold.Critical
18 - interface: xyz.openbmc_project.Sensor.Threshold.Critical
22 - name: board 0 fan 5 critical alarm assert
25 paths: board 0 fan 5 current critical alarm path group
29 - name: board 0 fan 5 critical alarm deassert
[all …]
H A Dboard-0-fan-9.yaml1 - name: board 0 fan 9 current critical alarm path group
5 - meta: PATH
7 - meta: PATH
10 - name: current fan critical alarm property
13 type: boolean
15 - interface: xyz.openbmc_project.Sensor.Threshold.Critical
18 - interface: xyz.openbmc_project.Sensor.Threshold.Critical
22 - name: board 0 fan 9 critical alarm assert
25 paths: board 0 fan 9 current critical alarm path group
29 - name: board 0 fan 9 critical alarm deassert
[all …]
H A Dboard-1-fan-3.yaml1 - name: board 1 fan 3 current critical alarm path group
5 - meta: PATH
7 - meta: PATH
10 - name: current fan critical alarm property
13 type: boolean
15 - interface: xyz.openbmc_project.Sensor.Threshold.Critical
18 - interface: xyz.openbmc_project.Sensor.Threshold.Critical
22 - name: board 1 fan 3 critical alarm assert
25 paths: board 1 fan 3 current critical alarm path group
29 - name: board 1 fan 3 critical alarm deassert
[all …]
H A Dboard-0-fan-8.yaml1 - name: board 0 fan 8 current critical alarm path group
5 - meta: PATH
7 - meta: PATH
10 - name: current fan critical alarm property
13 type: boolean
15 - interface: xyz.openbmc_project.Sensor.Threshold.Critical
18 - interface: xyz.openbmc_project.Sensor.Threshold.Critical
22 - name: board 0 fan 8 critical alarm assert
25 paths: board 0 fan 8 current critical alarm path group
29 - name: board 0 fan 8 critical alarm deassert
[all …]
H A Dboard-1-fan-6.yaml1 - name: board 1 fan 6 current critical alarm path group
5 - meta: PATH
7 - meta: PATH
10 - name: current fan critical alarm property
13 type: boolean
15 - interface: xyz.openbmc_project.Sensor.Threshold.Critical
18 - interface: xyz.openbmc_project.Sensor.Threshold.Critical
22 - name: board 1 fan 6 critical alarm assert
25 paths: board 1 fan 6 current critical alarm path group
29 - name: board 1 fan 6 critical alarm deassert
[all …]
H A Dboard-1-fan-11.yaml1 - name: board 1 fan 11 current critical alarm path group
5 - meta: PATH
7 - meta: PATH
10 - name: current fan critical alarm property
13 type: boolean
15 - interface: xyz.openbmc_project.Sensor.Threshold.Critical
18 - interface: xyz.openbmc_project.Sensor.Threshold.Critical
22 - name: board 1 fan 11 critical alarm assert
25 paths: board 1 fan 11 current critical alarm path group
29 - name: board 1 fan 11 critical alarm deassert
[all …]
H A Dboard-1-fan-2.yaml1 - name: board 1 fan 2 current critical alarm path group
5 - meta: PATH
7 - meta: PATH
10 - name: current fan critical alarm property
13 type: boolean
15 - interface: xyz.openbmc_project.Sensor.Threshold.Critical
18 - interface: xyz.openbmc_project.Sensor.Threshold.Critical
22 - name: board 1 fan 2 critical alarm assert
25 paths: board 1 fan 2 current critical alarm path group
29 - name: board 1 fan 2 critical alarm deassert
[all …]
H A Dboard-0-fan-4.yaml1 - name: board 0 fan 4 current critical alarm path group
5 - meta: PATH
7 - meta: PATH
10 - name: current fan critical alarm property
13 type: boolean
15 - interface: xyz.openbmc_project.Sensor.Threshold.Critical
18 - interface: xyz.openbmc_project.Sensor.Threshold.Critical
22 - name: board 0 fan 4 critical alarm assert
25 paths: board 0 fan 4 current critical alarm path group
29 - name: board 0 fan 4 critical alarm deassert
[all …]
H A Dboard-1-fan-10.yaml1 - name: board 1 fan 10 current critical alarm path group
5 - meta: PATH
7 - meta: PATH
10 - name: current fan critical alarm property
13 type: boolean
15 - interface: xyz.openbmc_project.Sensor.Threshold.Critical
18 - interface: xyz.openbmc_project.Sensor.Threshold.Critical
22 - name: board 1 fan 10 critical alarm assert
25 paths: board 1 fan 10 current critical alarm path group
29 - name: board 1 fan 10 critical alarm deassert
[all …]
H A Dboard-1-fan-7.yaml1 - name: board 1 fan 7 current critical alarm path group
5 - meta: PATH
7 - meta: PATH
10 - name: current fan critical alarm property
13 type: boolean
15 - interface: xyz.openbmc_project.Sensor.Threshold.Critical
18 - interface: xyz.openbmc_project.Sensor.Threshold.Critical
22 - name: board 1 fan 7 critical alarm assert
25 paths: board 1 fan 7 current critical alarm path group
29 - name: board 1 fan 7 critical alarm deassert
[all …]
H A Dboard-0-fan-0.yaml1 - name: board 0 fan 0 current critical alarm path group
5 - meta: PATH
7 - meta: PATH
10 - name: current fan critical alarm property
13 type: boolean
15 - interface: xyz.openbmc_project.Sensor.Threshold.Critical
18 - interface: xyz.openbmc_project.Sensor.Threshold.Critical
22 - name: board 0 fan 0 critical alarm assert
25 paths: board 0 fan 0 current critical alarm path group
29 - name: board 0 fan 0 critical alarm deassert
[all …]
/openbmc/pldm/libpldmresponder/examples/fru/
H A DFRU_Master.json1 // This is the master config file for generating PLDM FRU records from the D-Bus
2 // inventory objects. "service" is the name of D-Bus service hosting the
3 // inventory D-Bus objects, "root_path" is the root path for all the inventory
4 // D-Bus objects and "entities" section specifies the type of FRU's for which
7 // records will be created for all FRU's of type Board and CPU. The "entity_type"
8 // field is the PLDM entity type for Board and CPU. For each FRU type,
11 // record for FRU of type Board and Board_VINI.json is the config to generate
12 // the OEM record (VINI is a record in IBM IPZ VPD format) for FRU of type Board.
19 "interface": "xyz.openbmc_project.Inventory.Item.Board",
/openbmc/u-boot/board/samsung/common/
H A Dexynos5-dt-types.c1 // SPDX-License-Identifier: GPL-2.0+
15 #include <samsung/exynos5-dt-types.h>
27 * Odroix XU3/XU4/HC1/HC2 board revisions (from HC1+_HC2_MAIN_REV0.1_20171017.pdf):
28 * Rev ADCmax Board
30 * 0.2 372 XU3 0.2 | XU3L - no DISPLAYPORT (probe I2C0:0x40 / INA231)
34 * 0.6 1309 XU4-HC1 0.1
35 * 0.7 1470 XU4-HC1+ 0.1 (HC2)
53 if (odroid_info[i].board_type == gd->board_type) in odroid_get_rev()
75 while (retries--) { in odroid_get_adc_val()
87 if ((100 * abs(*adcval - adcval_prev) / adcval_prev) < 3) in odroid_get_adc_val()
[all …]
/openbmc/linux/drivers/comedi/drivers/
H A Daddi_apci_1516.c1 // SPDX-License-Identifier: GPL-2.0+
4 * Copyright (C) 2004,2005 ADDI-DATA GmbH for the source code of this module.
7 * ADDI-DATA GmbH
9 * D-77833 Ottersweier
10 * Tel: +19(0)7223/9493-0
11 * Fax: +49(0)7223/9493-92
12 * http://www.addi-data.com
13 * info@addi-data.com
22 * PCI bar 1 I/O Register map - Digital input/output
28 * PCI bar 2 I/O Register map - Watchdog (APCI-1516 and APCI-2016)
[all …]
H A Ddas08.c1 // SPDX-License-Identifier: GPL-2.0+
6 * COMEDI - Linux Control and Measurement Device Interface
21 * 'ai_encoding' member of board structure:
29 * complete, MSB[7] is an "over-range" bit.
161 status = inb(dev->iobase + DAS08_STATUS_REG); in das08_ai_eoc()
164 return -EBUSY; in das08_ai_eoc()
171 const struct das08_board_struct *board = dev->board_ptr; in das08_ai_insn_read() local
172 struct das08_private_struct *devpriv = dev->private; in das08_ai_insn_read()
179 chan = CR_CHAN(insn->chanspec); in das08_ai_insn_read()
180 range = CR_RANGE(insn->chanspec); in das08_ai_insn_read()
[all …]
/openbmc/u-boot/doc/
H A DREADME.sh2 U-Boot for Renesas SuperH
7 This file contains status information for the port of U-Boot to the
15 started the porting to u-boot in 2007.
24 This CPU has the SH4AL-DSP core.
30 This CPU has the SH3-DSP core and Ethernet controller.
39 Board specific code is in board/ms7750se
40 To use this board, type "make ms7750se_config".
42 - SCIF
43 - SDRAM
44 - NOR Flash
[all …]
/openbmc/linux/Documentation/arch/sh/
H A Dnew-machine.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Adding a new board to LinuxSH
7 Paul Mundt <lethal@linux-sh.org>
18 of the board-specific code (with the exception of stboards) ended up
19 in arch/sh/kernel/ directly, with board-specific headers ending up in
20 include/asm-sh/. For the new kernel, things are broken out by board type,
21 companion chip type, and CPU type. Looking at a tree view of this directory
24 Board-specific code::
27 |-- arch
28 | `-- sh
[all …]
/openbmc/u-boot/tools/buildman/
H A Dcmdline.py1 # SPDX-License-Identifier: GPL-2.0+
16 parser.add_option('-b', '--branch', type='string',
18 parser.add_option('-B', '--bloat', dest='show_bloat',
20 help='Show changes in function code size for each board')
21 parser.add_option('--boards', type='string', action='append',
22 help='List of board names to build separated by comma')
23 parser.add_option('-c', '--count', dest='count', type='int',
24 default=-1, help='Run build on the top n commits')
25 parser.add_option('-C', '--force-reconfig', dest='force_reconfig',
28 parser.add_option('-d', '--detail', dest='show_detail',
[all …]
/openbmc/u-boot/test/py/
H A DREADME.md1 # U-Boot pytest suite
5 This tool aims to test U-Boot by executing U-Boot shell commands using the
6 console interface. A single top-level script exists to execute or attach to the
7 U-Boot console, run the entire script of tests against it, and summarize the
10 - Testing is performed in the same way a user or script would interact with
11 U-Boot; there can be no disconnect.
12 - There is no need to write or embed test-related code into U-Boot itself.
13 It is asserted that writing test-related code in Python is simpler and more
15 - It is reasonably simple to interact with U-Boot in this way.
19 The test suite is implemented using pytest. Interaction with the U-Boot console
[all …]

12345678910>>...44