On Mon, 29 Jun 2015 13:44:04 +0200, Michael Allwright wrote: > I tried your patch today and although it is a cleaner implementation > than what I had, I'm still getting the same results as I did on > Friday. When both devices are configured, the ttySC2,3 shows up in > /dev but I can not get any RX or TX using picocom. I use the device > tree to instantiate the devices and when only one device is present > there are no issues (that is after the "fix FIFO address of secondary > UART" from Bo is applied - > http://www.spinics.net/lists/linux-serial/msg17820.html). > > Here is the relevant parts of my device tree that are declared under > the second I2C bus, and would stress the point, that if I comment out > one of either "uart56: sc16is762@48" or "uart78: sc16is762@49", the > other device works as expected, so this is definitely a software > problem and not a hardware / device configuration problem. Yeah, we are using port number to tell the chip line number. Will cook up a patch soon. > Regarding not working on tty-next, I'm not actually sure what the > correct workflow for resolving these sort of issues with the community > is. Since I'm also working with linux-media who also have their own > tree, I have been pulling the changes back and forth into my the > mainline kernel for my application as patches. Perhaps there is a > better way? You could probably just merge linux-media into your tree, it doesn't have very many patches. But no worries, I think we got the cause of the problem now. -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
