asustor-platform-driver
asustor-platform-driver copied to clipboard
Support for AS6706T is confirmed
Just letting you know support for the AS6706T platform is confirmed. Your assumptions about the GPIO pins for disks 5 and 6 are also correct. (As suggested in your asustor.c file.)
Thanks for confirming my assumptions about the SATA 5 and 6 LEDs! I made the corresponding changes in #16, can you test them? :)
@DanielGibson I can confirm that your code lines up with what I have. I made some tweeks to use the red LED's for activity and green for power.
LED CONFIG SETTINGS:
{
.name = "sata5:green:disk", // 17
.default_state = LEDS_GPIO_DEFSTATE_ON,
//.default_trigger = "disk-activity",
},
{ .name = "sata5:red:disk",
.default_state = LEDS_GPIO_DEFSTATE_ON, // 18
.default_trigger = "disk-activity"},
{
.name = "sata6:green:disk", // 19
.default_state = LEDS_GPIO_DEFSTATE_ON,
//.default_trigger = "disk-activity",
},
{ .name = "sata6:red:disk",
.default_state = LEDS_GPIO_DEFSTATE_ON, // 20
.default_trigger = "disk-activity"},
};
GPIO DRIVER:
GPIO_LOOKUP_IDX(GPIO_IT87, 61, NULL, 17, GPIO_ACTIVE_HIGH), // sata5:green:disk
GPIO_LOOKUP_IDX(GPIO_IT87, 62, NULL, 18, GPIO_ACTIVE_LOW), // sata5:red:disk
GPIO_LOOKUP_IDX(GPIO_IT87, 58, NULL, 19, GPIO_ACTIVE_HIGH), // sata6:green:disk
GPIO_LOOKUP_IDX(GPIO_IT87, 60, NULL, 20, GPIO_ACTIVE_LOW), // sata6:red:disk
Did you also make those changes for SATA1-4 or is my code for SATA5/6 not consistent with the existing behavior of 1-4?
@DanielGibson I also made those changes for 1-4. Your code is consistent. I just changed it to my liking.