Home
last modified time | relevance | path

Searched full:daa (Results 1 – 14 of 14) sorted by relevance

/linux/Documentation/driver-api/i3c/
H A Dprotocol.rst65 The discovery mechanism is called DAA (Dynamic Address Assignment), because it
68 During DAA, each I3C device reports 3 important things:
86 During DAA, each device on the bus has been assigned an address, and this
151 passed the device address (dynamic address assigned during DAA), a payload
/linux/Documentation/devicetree/bindings/i3c/
H A Di3c.yaml27 All I3C devices are supposed to support DAA (Dynamic Address Assignment),
36 specific I3C dynamic address before the DAA takes place (so that other
/linux/include/linux/i3c/
H A Dmaster.h176 * before starting DAA (Dynamic Address Assignment)
324 * ease the DAA (Dynamic Address Assignment) procedure (see
380 * can be after a DAA or when a device is statically declared
397 * @do_daa: do a DAA (Dynamic Address Assignment) procedure. This is procedure
399 * discovered sure the DAA using i3c_master_add_i3c_dev_locked().
/linux/drivers/i3c/
H A Dmaster.c35 * - re-triggering DAA
906 * i3c_master_entdaa_locked() - start a DAA (Dynamic Address Assignment)
910 * Send a ENTDAA CCC command to start a DAA procedure.
1011 * words, after the DAA procedure has finished) and instantiated in
1661 * i3c_master_do_daa() - do a DAA (Dynamic Address Assignment)
1662 * @master: master doing the DAA
1806 * 6. Do a DAA (Dynamic Address Assignment) to assign dynamic addresses to all
1891 /* Disable all slave events before starting DAA. */ in i3c_master_bus_init()
1902 * the requested init_dyn_addr is retried after DAA is done in in i3c_master_bus_init()
1928 * DAA happens, and the requested dynamic address will in i3c_master_bus_init()
[all …]
/linux/drivers/i3c/master/mipi-i3c-hci/
H A Dcmd_v1.c305 * DAA, register the device which will allocate its own DAT entry in hci_cmd_v1_daa()
320 DBG("next_addr = 0x%02x, DAA using DAT %d", next_addr, dat_idx); in hci_cmd_v1_daa()
/linux/drivers/i3c/master/
H A Dsvc-i3c-master.c857 /* SVC_I3C_MCTRL_REQUEST_PROC_DAA have two mode, ENTER DAA or PROCESS DAA. in svc_i3c_master_do_daa_locked()
859 * ENTER DAA: in svc_i3c_master_do_daa_locked()
863 * PROCESS DAA: in svc_i3c_master_do_daa_locked()
913 * address, this is the natural end of the DAA in svc_i3c_master_do_daa_locked()
935 * allowed only once, DAA will be stopped and in svc_i3c_master_do_daa_locked()
971 dev_dbg(master->dev, "DAA: device %d assigned to 0x%02x\n", in svc_i3c_master_do_daa_locked()
H A Di3c-master-cdns.c1143 /* Prepare RR slots before launching DAA. */ in cdns_i3c_master_do_daa()
1165 * Clear all retaining registers filled during DAA. We already in cdns_i3c_master_do_daa()
H A Ddw-i3c-master.c843 /* Prepare DAT before launching DAA. */ in dw_i3c_master_daa()
/linux/drivers/md/
H A Ddm-writecache.c309 long daa; in persistent_memory_claim() local
311 daa = dax_direct_access(wc->ssd_dev->dax_dev, offset + i, in persistent_memory_claim()
313 if (daa <= 0) { in persistent_memory_claim()
314 r = daa ? daa : -EINVAL; in persistent_memory_claim()
321 while (daa-- && i < p) { in persistent_memory_claim()
/linux/arch/m68k/ifpsp060/
H A Dftest.sa134 dc.l $feb861ff,$00000d84,$4a0066ff,$00000daa
/linux/drivers/net/ethernet/sun/
H A Dsungem.h632 * is programmed in the "Bit-Bang" mode. The daa will be steered to the
/linux/arch/x86/kernel/
H A Duprobes.c120 * 27,2f,37,3f - formerly daa/das/aaa/aas
/linux/tools/arch/x86/lib/
H A Dx86-opcode-map.txt87 27: DAA (i64)
/linux/sound/pci/
H A Dcmipci.c230 #define CM_MMODE_MASK 0x00000E00 /* model DAA interface mode */