Home
last modified time | relevance | path

Searched refs:ping (Results 1 – 102 of 102) sorted by relevance

/linux-4.4.14/drivers/watchdog/
Dmax63xx_wdt.c55 void (*ping)(struct max63xx_wdt *wdt); member
123 wdt->ping(wdt); in max63xx_wdt_ping()
135 wdt->ping(wdt); in max63xx_wdt_start()
151 .ping = max63xx_wdt_ping,
197 wdt->ping = max63xx_mmap_ping; in max63xx_mmap_init()
Dsp805_wdt.c124 static int wdt_config(struct watchdog_device *wdd, bool ping) in wdt_config() argument
129 if (!ping) { in wdt_config()
143 if (!ping) { in wdt_config()
198 .ping = wdt_ping,
Dbcm47xx_wdt.c95 .ping = bcm47xx_wdt_hard_keepalive,
187 .ping = bcm47xx_wdt_soft_keepalive,
Dep93xx_wdt.c106 .ping = ep93xx_wdt_keepalive,
Dux500_wdt.c76 .ping = ux500_wdt_keepalive,
Dwatchdog_dev.c76 if (wdd->ops->ping) in watchdog_ping()
77 err = wdd->ops->ping(wdd); /* ping the watchdog */ in watchdog_ping()
Dintel-mid_wdt.c111 .ping = wdt_ping,
Dretu_wdt.c105 .ping = retu_wdt_ping,
Dwm8350_wdt.c131 .ping = wm8350_wdt_ping,
Dbooke_wdt.c204 .ping = booke_wdt_ping,
Dda9055_wdt.c139 .ping = da9055_wdt_ping,
Drt2880_wdt.c131 .ping = rt288x_wdt_ping,
Dtxx9wdt.c95 .ping = txx9wdt_ping,
Dsirfsoc_wdt.c130 .ping = sirfsoc_wdt_updatetimeout,
Dmenf21bmc_wdt.c114 .ping = menf21bmc_wdt_ping,
Dda9052_wdt.c171 .ping = da9052_wdt_ping,
Drn5t618_wdt.c143 .ping = rn5t618_wdt_ping,
Dvia_wdt.c147 .ping = wdt_ping,
Djz4740_wdt.c142 .ping = jz4740_wdt_ping,
Dda9063_wdt.c150 .ping = da9063_wdt_ping,
Dmeson_wdt.c137 .ping = meson_wdt_ping,
Ddavinci_wdt.c152 .ping = davinci_wdt_ping,
Dqcom-wdt.c78 .ping = qcom_wdt_ping,
Ddiag288_wdt.c199 .ping = wdt_ping,
Dof_xilinx_wdt.c118 .ping = xilinx_wdt_keepalive,
Dmpc8xxx_wdt.c140 .ping = mpc8xxx_wdt_ping,
Dtegra_wdt.c185 .ping = tegra_wdt_ping,
Dda9062_wdt.c187 .ping = da9062_wdt_ping,
Dmena21_wdt.c136 .ping = a21_wdt_ping,
Die6xx_wdt.c183 .ping = ie6xx_wdt_ping,
Dgpio_wdt.c159 .ping = gpio_wdt_ping,
Dmtk_wdt.c162 .ping = mtk_wdt_ping,
Dsama5d4_wdt.c114 .ping = sama5d4_wdt_ping,
Dwm831x_wdt.c180 .ping = wm831x_wdt_ping,
Dshwdt.c211 .ping = sh_wdt_keepalive,
Dimgpdc_wdt.c166 .ping = pdc_wdt_keepalive,
Dst_lpc_wdt.c173 .ping = st_wdog_keepalive,
Dlpc18xx_wdt.c169 .ping = lpc18xx_wdt_feed,
Dsunxi_wdt.c209 .ping = sunxi_wdt_ping,
Dcadence_wdt.c279 .ping = cdns_wdt_reload,
Domap_wdt.c225 .ping = omap_wdt_ping,
Dcoh901327_wdt.c244 .ping = coh901327_ping,
Dimx2_wdt.c214 .ping = imx2_wdt_ping,
Docteon-wdt-main.c547 .ping = octeon_wdt_ping,
DiTCO_wdt.c384 .ping = iTCO_wdt_ping,
Dkempld_wdt.c437 .ping = kempld_wdt_keepalive,
Ds3c2410_wdt.c366 .ping = s3c2410wdt_keepalive,
Dorion_wdt.c368 .ping = orion_wdt_ping,
/linux-4.4.14/Documentation/
DIRQ-affinity.txt28 [root@moon 44]# ping -f h
31 --- hell ping statistics ---
45 [root@moon 44]# ping -f h
48 --- hell ping statistics ---
/linux-4.4.14/tools/testing/selftests/ftrace/test.d/event/
Dtoplevel-enable.tc16 ping localhost -c 1 || sleep .001 || usleep 1 || sleep 1
Dsubsystem-enable.tc16 ping localhost -c 1 || sleep .001 || usleep 1 || sleep 1
Devent-enable.tc16 ping localhost -c 1 || sleep .001 || usleep 1 || sleep 1
/linux-4.4.14/drivers/staging/lustre/lustre/mgc/
Dlproc_mgc.c49 LPROC_SEQ_FOPS_WR_ONLY(mgc, ping);
/linux-4.4.14/Documentation/watchdog/
Dwatchdog-kernel-api.txt99 int (*ping)(struct watchdog_device *);
139 that regularly sends a keepalive ping to the watchdog timer hardware.
144 * ping: this is the routine that sends a keepalive ping to the watchdog timer
150 the watchdog timer driver core does: to send a keepalive ping to the watchdog
151 timer hardware it will either use the ping operation (when available) or the
152 start operation (when the ping operation is not available).
Dwatchdog-api.txt38 timeout or margin. The simplest way to ping the watchdog is to write
43 still responding before doing the write call to ping the watchdog.
193 WDIOF_KEEPALIVEPING Keep alive ping reply
195 The watchdog saw a keepalive ping since it was last queried.
Dconvert_drivers_to_kernel_api.txt24 also serves as the ping-function. If that is the case and you need start/stop
30 i.e. ping on write and magic char ('V') handling.
130 + .ping = s3c2410wdt_keepalive,
/linux-4.4.14/Documentation/mic/mpssd/
Dmpss89 ping -c 1 $ipaddr &> /dev/null
/linux-4.4.14/include/linux/
Dwatchdog.h44 int (*ping)(struct watchdog_device *); member
/linux-4.4.14/drivers/ntb/test/
DKconfig4 This is a simple ping pong driver that exercises the scratchpads and
/linux-4.4.14/drivers/net/ethernet/intel/ixgbe/
Dixgbe_sriov.c1192 u32 ping; in ixgbe_ping_vf() local
1194 ping = IXGBE_PF_CONTROL_MSG; in ixgbe_ping_vf()
1196 ping |= IXGBE_VT_MSGTYPE_CTS; in ixgbe_ping_vf()
1197 ixgbe_write_mbx(hw, &ping, 1, vf); in ixgbe_ping_vf()
1203 u32 ping; in ixgbe_ping_all_vfs() local
1207 ping = IXGBE_PF_CONTROL_MSG; in ixgbe_ping_all_vfs()
1209 ping |= IXGBE_VT_MSGTYPE_CTS; in ixgbe_ping_all_vfs()
1210 ixgbe_write_mbx(hw, &ping, 1, i); in ixgbe_ping_all_vfs()
/linux-4.4.14/Documentation/usb/
Dgadget-testing.txt84 On the device: ping <host's IP>
85 On the host: ping <device's IP>
117 On the device: ping <host's IP>
118 On the host: ping <device's IP>
150 On the device: ping <host's IP>
151 On the host: ping <device's IP>
408 On the device: ping <host's IP>
409 On the host: ping <device's IP>
532 On the device: ping <host's IP>
533 On the host: ping <device's IP>
DWUSB-Design-overview.txt329 if the activity timestamp gets old, we ping the device by sending it a
/linux-4.4.14/net/ipv6/
DMakefile10 raw.o icmp.o mcast.o reassembly.o tcp_ipv6.o ping.o \
/linux-4.4.14/drivers/input/mouse/
Dcyapa_gen6.c414 u8 ping[] = { 0x04, 0x00, 0x05, 0x00, 0x2f, 0x00, 0x00 }; in cyapa_gen6_deep_sleep() local
422 cyapa_i2c_pip_write(cyapa, ping, sizeof(ping)); in cyapa_gen6_deep_sleep()
/linux-4.4.14/net/ipv4/
DMakefile15 inet_fragment.o ping.o ip_tunnel_core.o gre_offload.o
/linux-4.4.14/Documentation/networking/
Dipsec.txt33 The result is much more wired to the user when ping peer with different
DREADME.sb1000112 10.) Try pinging a site via `ping -c 5 www.yahoo.com', for example. You should
118 If this doesn't help, try something like `ping -c 5 204.71.200.67' to
130 interface. It looks like I'm connected but I can't even ping any
Dbatman-adv.txt120 # NodeB: ping 192.168.0.1
182 the moment the batctl contains ping, traceroute, tcpdump and
Dnetconsole.txt181 ping -c 1 10.0.0.2 ; /sbin/arp -n | grep 10.0.0.2
Dde4x5.txt88 using ping showed that it appears to work....
D3c509.txt146 interrupt line. If the device is receiving packets but 'ping' doesn't work,
Ddl2k.txt44 Now eth0 should active, you can test it by "ping" or get more information by
Deql.txt7 to increase your bandwidth. It will not reduce your latency (i.e. ping
Dl2tp.txt242 # ping 10.5.1.1
Dixgb.txt99 ping <IP_address>
Dcs89x0.txt303 with large ping packets consumes 82% of its CPU capacity in non-DMA
Drxrpc.txt197 (*) ACK'ing is handled by the protocol driver automatically, including ping
Dbonding.txt2540 a "ping" to some other host on the network, and noticing that the
2541 output from ping flags duplicates (typically one per slave).
2546 # ping -n 10.0.4.2
/linux-4.4.14/drivers/staging/lustre/lustre/mdc/
Dlproc_mdc.c161 LPROC_SEQ_FOPS_WR_ONLY(mdc, ping);
/linux-4.4.14/drivers/staging/lustre/lnet/selftest/
Drpc.h204 test_ping_req_t ping; member
Dframework.c713 test_ping_req_t *ping = &req->tsr_u.ping; in sfw_unpack_addtest_req() local
715 __swab32s(&ping->png_size); in sfw_unpack_addtest_req()
716 __swab32s(&ping->png_flags); in sfw_unpack_addtest_req()
Dselftest.h387 test_ping_req_t ping; /* ping parameter */ member
Dconrpc.c777 test_ping_req_t *prq = &req->tsr_u.ping; in lstcon_pingrpc_prep()
/linux-4.4.14/Documentation/gpio/
Ddrivers-on-gpio.txt77 that will periodically "ping" a hardware connected to a GPIO line by toggling
78 it from 1-to-0-to-1. If that hardware does not recieve its "ping"
/linux-4.4.14/Documentation/video4linux/cx2341x/
Dfw-upload.txt30 - Write 0x00000000 to register 0xA064 to ping? the APU.
/linux-4.4.14/drivers/misc/mei/
Dwd.c343 .ping = mei_wd_ops_ping,
/linux-4.4.14/Documentation/thermal/
Dnouveau_thermal79 inquiries, please ping mupuf on IRC (#nouveau, freenode).
Dintel_powerclamp.txt231 effectiveness. The extreme case would be doing a ping -f to generated
/linux-4.4.14/drivers/usb/isp1760/
Disp1760-hcd.c149 u32 ping; member
589 ptd->dw3 |= TO_DW3_PING(qh->ping); in create_ptd_atl()
1149 qh->ping = FROM_DW3_PING(ptd.dw3); in handle_done_ptds()
1161 qh->ping = FROM_DW3_PING(ptd.dw3); in handle_done_ptds()
1177 qh->ping = 0; in handle_done_ptds()
/linux-4.4.14/Documentation/locking/
Drt-mutex.txt73 optimization the higher-prio thread would ping-pong to the lower-prio
/linux-4.4.14/Documentation/filesystems/nfs/
Dnfs-rdma.txt194 host1$ ping a.b.c.y
195 host2$ ping a.b.c.x
/linux-4.4.14/drivers/hwmon/
Dsch56xx-common.c416 .ping = watchdog_trigger,
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-class-mic.txt165 alternative means such as a network ping. This setting is
/linux-4.4.14/Documentation/isdn/
DREADME413 Now you are ready! A ping to the set address should now result in an
461 you test this feature by using ping, some routers will re-dial very
463 In this case use ping with the option -i <sec> to increase the interval
DREADME.sc205 x) a ping should result in the establishment of the connection
/linux-4.4.14/drivers/scsi/qla4xxx/
Dql4_def.h375 } ping; member
Dql4_os.c5213 e->u.ping.status = status; in qla4xxx_post_ping_evt_work()
5214 e->u.ping.pid = pid; in qla4xxx_post_ping_evt_work()
5215 e->u.ping.data_size = data_size; in qla4xxx_post_ping_evt_work()
5216 memcpy(e->u.ping.data, data, data_size); in qla4xxx_post_ping_evt_work()
5247 e->u.ping.status, in qla4xxx_do_work()
5248 e->u.ping.pid, in qla4xxx_do_work()
5249 e->u.ping.data_size, in qla4xxx_do_work()
5250 e->u.ping.data); in qla4xxx_do_work()
/linux-4.4.14/drivers/staging/lustre/lustre/osc/
Dlproc_osc.c577 LPROC_SEQ_FOPS_WR_ONLY(osc, ping);
/linux-4.4.14/net/
DKconfig68 allows you to ping yourself (great fun, that!).
/linux-4.4.14/drivers/net/ethernet/intel/igb/
Digb_main.c5681 u32 ping; in igb_ping_all_vfs() local
5685 ping = E1000_PF_CONTROL_MSG; in igb_ping_all_vfs()
5687 ping |= E1000_VT_MSGTYPE_CTS; in igb_ping_all_vfs()
5688 igb_write_mbx(hw, &ping, 1, i); in igb_ping_all_vfs()
/linux-4.4.14/Documentation/s390/
DDebugging390.txt2073 Now ping the device from a machine in the same subnet.
2080 ping -c 5 <broadcast_addr> i.e. the Bcast field above in the output of
/linux-4.4.14/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt976 You are not talking to the UML when you ping that interface and get a
1066 You should be able to ping the host at this point.