sorry about delay, but I am travelling these days…
Ok, so it looks like the regulator config is different on your board, compared to DB410c… And the problem is that our binary images only support db410c. It probably worked before ‘by accident’ and we moved to a newer kernel the regulator that you relied on is no longer turned on.
I still haven’t been able to try on DB410c myself, have you tried? what’s the behavior on db410c?
If we start having board level difference between DB410c and their derived boards (like yours), this opens a new set of issues that we are going to have to deal with… which starts with device tree management. I suppose that you might be reusing the device tree from db410c on your own hardware, or do you have your own?
Based on the board differences, we might end with different DTB for each board. If we need more than just DTB differences, and need actual kernel patch, we will need to decide how we proceed with them. Mostly on a case by case basis.