config USB_ISP1760 tristate "NXP ISP 1760/1761 support" depends on USB || USB_GADGET help Say Y or M here if your system as an ISP1760 USB host controller or an ISP1761 USB dual-role controller. This driver does not support isochronous transfers or OTG. This USB controller is usually attached to a non-DMA-Master capable bus. NXP's eval kit brings this chip on PCI card where the chip itself is behind a PLB to simulate such a bus. To compile this driver as a module, choose M here: the module will be called isp1760. config USB_ISP1760_HCD bool config USB_ISP1761_UDC bool if USB_ISP1760 choice bool "ISP1760 Mode Selection" default USB_ISP1760_DUAL_ROLE if (USB && USB_GADGET) default USB_ISP1760_HOST_ROLE if (USB && !USB_GADGET) default USB_ISP1760_GADGET_ROLE if (!USB && USB_GADGET) config USB_ISP1760_HOST_ROLE bool "Host only mode" depends on USB=y || USB=USB_ISP1760 select USB_ISP1760_HCD help Select this if you want to use the ISP1760 in host mode only. The gadget function will be disabled. config USB_ISP1760_GADGET_ROLE bool "Gadget only mode" depends on USB_GADGET=y || USB_GADGET=USB_ISP1760 select USB_ISP1761_UDC help Select this if you want to use the ISP1760 in peripheral mode only. The host function will be disabled. config USB_ISP1760_DUAL_ROLE bool "Dual Role mode" depends on USB=y || USB=USB_ISP1760 depends on USB_GADGET=y || USB_GADGET=USB_ISP1760 select USB_ISP1760_HCD select USB_ISP1761_UDC help Select this if you want to use the ISP1760 in both host and peripheral modes. endchoice endif ec971323f8256e8005a32b6'>refslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Golle <daniel@makrotopia.org>2017-01-20 14:28:25 +0100
committerKalle Valo <kvalo@codeaurora.org>2017-01-28 09:03:45 +0200
commit5c4412e0728063583ec971323f8256e8005a32b6 (patch)
tree1b5fb249b6db699d5e22b09c699f18c64f1738f8
parent34db70b92faed22f59fdc1dba766e8cb6248fe9e (diff)
rt2x00: rt2800lib: add support for RT3352 with 20MHz crystal
On Rt3352 the driver needs to know the frequency of an external crystal which can be either 40 MHz (as on all other WiSoCs until now) or 20 MHz. Get the clock attached by ramips WiSoC platform code which probes SYSC_REG_SYSCFG (added by John Crispin in commit 6ac8579b96e3b) and introduce a new flag clk_is_20mhz in struct hw_mode_spec to make the driver aware and use either 40 MHz or 20 MHz specific rf_vals on those WiSoC platforms. The introduced support for boards with a 20 MHz crystal is also needed for RT5350. Signed-off-by: Daniel Golle <daniel@makrotopia.org> Signed-off-by: Gabor Juhos <juhosg@openwrt.org> Signed-off-by: Mathias Kresin <dev@kresin.me> Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Diffstat
-rw-r--r--drivers/net/wireless/ralink/rt2x00/rt2800lib.c31
1 files changed, 30 insertions, 1 deletions
diff --git a/drivers/net/wireless/ralink/rt2x00/rt2800lib.c b/drivers/net/wireless/ralink/rt2x00/rt2800lib.c