Home
last modified time | relevance | path

Searched full:seem (Results 1 – 25 of 755) sorted by relevance

12345678910>>...31

/kernel/linux/linux-5.10/arch/sh/drivers/pci/
Dops-dreamcast.c27 * here, but since it doesn't seem that there is any such implementation in
33 * and the general lack of activity by DC hardware hackers, this doesn't seem
/kernel/linux/linux-5.10/sound/usb/line6/
Dtoneport.c495 .altsetting = 2, /* 1..4 seem to be ok */
504 .altsetting = 2, /* 1..4 seem to be ok */
513 .altsetting = 2, /* 1..4 seem to be ok */
531 .altsetting = 2, /* 1..4 seem to be ok */
540 .altsetting = 2, /* 1..4 seem to be ok */
/kernel/linux/linux-5.10/arch/powerpc/include/asm/
Duninorth.h48 * the AGP bus. It doesn't seem to be visible to the CPU as of UniNorth 1.x,
64 * cachable). AGP memory itself doesn't seem to be cache coherent neither.
78 * Turning on AGP seem to require a double invalidate operation, one before
Dsmu.h47 * This is a "mux" for fan control commands. The command seem to
49 * of argument, this seem to be queries for fans status, setpoint,
185 * both cases. They seem to be:
208 * This command seem to be a grab bag of various things
294 * This command seem to be a grab bag of various things
/kernel/linux/linux-5.10/Documentation/hwmon/
Dw83781d.rst424 PWM registers seem to be split in two parts: bit 7 is a mode selector,
425 while the other bits seem to define a value or threshold.
427 When bit 7 is clear, bits 6-0 seem to hold a threshold value. If the value
430 represents. Note that there seem to be some inertia in this mode, speed
435 When bit 7 is set, bits 3-0 seem to hold a threshold value, while bits 6-4
472 Changing the high nibble doesn't seem to do much except the high bit
473 (0x80) must be set for PWM to work, else the current pwm doesn't seem to
/kernel/linux/linux-5.10/Documentation/input/devices/
Dntrig.rst68 seem to be 12" sensors (Dell Latitude XT and XT2 and the HP TX2), and
87 seem to have different profiles. Ghost activity typically shows up as small
137 contacts are active they seem to be sorted primarily by Y position.
/kernel/linux/linux-5.10/drivers/staging/kpc2000/
DTODO1 - the kpc_spi driver doesn't seem to let multiple transactions (to different instances of the core)…
/kernel/linux/linux-5.10/arch/alpha/include/uapi/asm/
Dstatfs.h8 even seem to implement statfs64 */
/kernel/linux/linux-5.10/arch/arm64/boot/dts/amlogic/
Dmeson-gxl-s805x.dtsi13 /* The S805X Package doesn't seem to handle the 744MHz OPP correctly */
/kernel/linux/linux-5.10/drivers/staging/media/rkisp1/
DTODO5 in several places of the code, review this, specially that it doesn't seem it
/kernel/linux/linux-5.10/drivers/media/usb/gspca/
Dvicam.c117 req_data[2] = 0x90; /* unknown, does not seem to do anything */ in vicam_read_frame()
139 /* bytes 9-15 do not seem to affect exposure or image quality */ in vicam_read_frame()
191 /* Note the frame header contents seem to be completely in vicam_dostream()
/kernel/linux/linux-5.10/drivers/net/usb/
Dplusb.c82 /* some units seem to need this reset, others reject it utterly. in pl_reset()
95 /* some PL-2302 versions seem to fail usb_set_interface() */
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/rtc/
Dfaraday,ftrtc010.txt14 says the clock should be 1 Hz, but implementers actually seem
/kernel/linux/linux-5.10/include/uapi/asm-generic/
Dpoll.h13 /* The rest seem to be more-or-less nonstandard. Check them! */
/kernel/linux/linux-5.10/arch/arm/mach-omap2/
Dti81xx-restart.c22 * NOTE: Warm reset does not seem to work, may require resetting
/kernel/linux/linux-5.10/tools/lib/perf/Documentation/
Dmanpage-suppress-sp.xsl9 that some versions of docbook stylesheets seem to add -->
/kernel/linux/linux-5.10/tools/perf/Documentation/
Dmanpage-suppress-sp.xsl9 that some versions of docbook stylesheets seem to add -->
/kernel/linux/linux-5.10/tools/lib/traceevent/Documentation/
Dmanpage-suppress-sp.xsl9 that some versions of docbook stylesheets seem to add -->
/kernel/linux/linux-5.10/drivers/net/phy/
Dbcm84881.c90 /* disabled autoneg doesn't seem to work with this PHY */ in bcm84881_config_aneg()
185 /* disabled autoneg doesn't seem to work, so force the link in bcm84881_read_status()
/kernel/linux/linux-5.10/Documentation/i2c/busses/
Di2c-via.rst35 No error messages, but still i2c doesn't seem to work.
/kernel/linux/linux-5.10/include/uapi/linux/
Dposix_types.h9 * beyond that you'll have to change this too. But 1024 fd's seem to be
/kernel/linux/linux-5.10/Documentation/sound/cards/
Dmaya44.rst48 Things that do not seem to work:
50 - The level meters ("multi track") in 'alsamixer' do not seem to react to signals in (if this is a …
/kernel/linux/linux-5.10/Documentation/sound/hd-audio/
Drealtek-pc-beep.rst87 Realtek, is of note: unlike most registers, which seem to control detailed
125 seem to be close relatives of the ALC256. (They all share one initialization
/kernel/linux/linux-5.10/arch/hexagon/include/asm/
Dtlbflush.h37 * by logical address. There doesn't seem to be any possibility that they
/kernel/linux/linux-5.10/drivers/hwmon/
Dabituguru.c69 * However sometimes older versions of the uGuru seem to be distracted and they
619 * sensors, my version of the uGuru does seem to stop writing to them, the
652 ABIT_UGURU_DEBUG(2, " bank2 sensor %d does not seem " in abituguru_detect_no_bank2_sensors()
661 ABIT_UGURU_DEBUG(2, " bank2 sensor %d does not seem " in abituguru_detect_no_bank2_sensors()
670 ABIT_UGURU_DEBUG(2, " bank2 sensor %d does not seem " in abituguru_detect_no_bank2_sensors()
704 ABIT_UGURU_DEBUG(2, " pwm channel %d does not seem " in abituguru_detect_no_pwms()
721 ABIT_UGURU_DEBUG(2, " pwm channel %d does not seem " in abituguru_detect_no_pwms()
738 "not seem to be a pwm channel: " in abituguru_detect_no_pwms()
747 "not seem to be a pwm channel: " in abituguru_detect_no_pwms()
758 ABIT_UGURU_DEBUG(2, " pwm channel %d does not seem " in abituguru_detect_no_pwms()
[all …]

12345678910>>...31