[LEDE-DEV] Help on porting new device (DCS-933L)

[Luiz Angelo Daros de Luca]

I guess you was looking for something like this:

dcs933l_v1.13.05/dcs933l/RT288x_SDK/source/linux-2.6.21.x/drivers/char/ralink_gpio.h:
#define PUSH_BUTTON_1_IRQ   0
#define PUSH_BUTTON_2_IRQ   10
#define WPS_LED         13
#define POWER_LED       2
#define LINK_LED                9
#define LIGHT_SENSOR_IN         11
#define IR_LED_OUT_1            12
#define IR_LED_OUT_2            14
#define HW_ID_1                 1
#define CHIP_RESET              7
#define OV780_SPI_OUT       17
#define OV780_SPI_IN        18
#define PIR_IN          19
#define OV780_BOOT_IN       20

(All those GPIO that I know matched)

It seems to be used only by uvc_stream, which looks like the "camera client".
I'll start to study those GPIO. I guess it uses values different from 0/1.

Anyway, thanks for the tip. I did read about GPIO ports like
"usbpower" but I didn't (wasn't willing to)
believe that this was the problem. Factory firmware show those devices
normally, even when not "in use".

What would be the best way to deal with those GPIO that (possibly)
activate the camera?
Export those on DTS or do it in an app? Is it a good practice to
export all known GPIO (but not used) on DTS?

Regards,
---
     Luiz Angelo Daros de Luca, Me.
            luizluca at gmail.com


2016-12-14 6:22 GMT-02:00 Luiz Angelo Daros de Luca <luizluca at gmail.com>:
> Hi John,
>
> I did not get your mails. I just saw them on the maillist history.
>
> My device is labeled A1 (external tag). However, the ID on board is B1
> (and according to openwrt wiki, A1 should use a different SoC).
> If I consider only the external tag, it is DCS-933L A1. Anyway, A1 and
> A2 shares the same firmware.
>
> I already tried to use this script to set all GPIO to 0 or 1 without
> the webcam appearing.
> https://wiki.openwrt.org/doc/hardware/port.gpio#script_static
>
> Would it be enough? Or I need to somehow reset the usb hub? Could it
> be using some already reserved gpio?
>
> Regards,