linux-kernel - A question about MUSB driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Mon, 22 Jun 2009 11:29:07 +0300
From:	Pablo Bitton <pablo.bitton@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: A question about MUSB driver

Hello to all,

I have a question about "davinci_source_power()" function at
drivers/usb/musb/davinci.c
(http://lxr.linux.no/linux+v2.6.30/drivers/usb/musb/davinci.c#L170).

If I am not wrong, it is using "#ifdef CONFIG_MACH_DAVINCI_EVM" and
"machine_is_davinci_evm()"
macro to conditionally turn VBUS-controlling GPIO on and off,
depending on specific machine being DaVinci EVM.

Our team works on another DaVinci based board - that is based on the
EVM, but has different machine ID and uses
different GPIO for VBUS switching.

If we use "davinci.c" code without a change, it is compiled without
VBUS handling code at all, which is certainly not what we need.
How should we change the code/Makefile/build process to include VBUS
handling for out specific board?

Thanks in advance.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/