some u-boot mailing list
Hi Does anybody know some u-boot mailing list like here for linux, but for u-boot. Is someone subscribed maybe somewhere? I have question about what might be a potential rootcause of synchronous abort which I get when executing "i2c dev 1" in u-boot shell. ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
USB Question about devices being reconnected to the host
Hi,
I'm learning about USB drivers and I would like to know about
disconnecting and reconnecting usb devices.
I can see my probe function being called and also the disconnect
function. But if I reconnect the device there is no call from the kernel
to notify my driver about the device being reconnected.
I can also see that the module for my driver was not unloaded, so I dont
understand the life cycle of a USB device.
If the module is not unloaded at disconnection and re-loaded for a new
device being connected, how can the driver know the device is there
after a disconnection?
Thanks
Lucas
This is my dmesg for the driver at the end of this email:
[ 34.706041] usb 1-1.1.2: new high-speed USB device number 5 using dwc_otg
[ 34.837647] usb 1-1.1.2: New USB device found, idVendor=04b4,
idProduct=00f1, bcdDevice= 0.00
[ 34.837666] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[ 34.837679] usb 1-1.1.2: Product: FX3
[ 34.837693] usb 1-1.1.2: Manufacturer: Cypress
[ 34.902480] usbdev_probe
[ 34.902681] usbcore: registered new interface driver My USB Device
[ 45.416310] usb 1-1.1.2: USB disconnect, device number 5
[ 45.416655] usbdev_disconnect
[ 61.326035] usb 1-1.1.2: new high-speed USB device number 6 using dwc_otg
[ 61.457674] usb 1-1.1.2: New USB device found, idVendor=04b4,
idProduct=00f1, bcdDevice= 0.00
[ 61.457692] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[ 61.457706] usb 1-1.1.2: Product: FX3
[ 61.457720] usb 1-1.1.2: Manufacturer: Cypress
Driver:
#define DEBUG
#include
#include
#include
static int usbdev_probe(struct usb_interface *intf, const struct
usb_device_id *id)
{
pr_info("%s", __func__);
return 0;
}
static void usbdev_disconnect(struct usb_interface *intf)
{
pr_info("%s", __func__);
}
static int usbdev_suspend(struct usb_interface *intf, pm_message_t message)
{
pr_err("%s", __func__);
return 0;
}
static int usbdev_resume(struct usb_interface *intf)
{
pr_info("%s", __func__);
return 0;
}
static int usbdev_reset_resume(struct usb_interface *intf)
{
pr_info("%s", __func__);
return 0;
}
static int usbdev_pre_reset(struct usb_interface *intf)
{
pr_info("%s", __func__);
return 0;
}
static int usbdev_post_reset(struct usb_interface *intf)
{
pr_info("%s", __func__);
return 0;
}
static const struct usb_device_id usbdev_id_table[] = {
{ USB_DEVICE(0x04b4, 0x00f1) },
{}
};
MODULE_DEVICE_TABLE(usb, usbdev_id_table);
static struct usb_driver usbdev_driver = {
.name = "My USB Device",
.probe = usbdev_probe,
.disconnect = usbdev_disconnect,
.id_table = usbdev_id_table,
.suspend= usbdev_suspend,
.resume = usbdev_resume,
.reset_resume = usbdev_reset_resume,
.pre_reset = usbdev_pre_reset,
.post_reset = usbdev_post_reset,
};
module_usb_driver(usbdev_driver);
MODULE_AUTHOR("Lucas Tanure ");
MODULE_DESCRIPTION("Driver for My USB device");
MODULE_LICENSE("GPL v2");
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: USB Question about devices being reconnected to the host
On Thu, Oct 15, 2020 at 01:17:45PM +0100, Lucas Tanure wrote: > Hi, > > I'm learning about USB drivers and I would like to know about disconnecting > and reconnecting usb devices. > > I can see my probe function being called and also the disconnect function. > But if I reconnect the device there is no call from the kernel to notify my > driver about the device being reconnected. That's not good, your driver should be told this. > I can also see that the module for my driver was not unloaded, so I dont > understand the life cycle of a USB device. Modules are never auto-unloaded. > If the module is not unloaded at disconnection and re-loaded for a new > device being connected, how can the driver know the device is there after a > disconnection? The probe function should be called, are you sure it isn't? > > Thanks > Lucas > > This is my dmesg for the driver at the end of this email: > > [ 34.706041] usb 1-1.1.2: new high-speed USB device number 5 using dwc_otg > [ 34.837647] usb 1-1.1.2: New USB device found, idVendor=04b4, > idProduct=00f1, bcdDevice= 0.00 > [ 34.837666] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, > SerialNumber=0 > [ 34.837679] usb 1-1.1.2: Product: FX3 > [ 34.837693] usb 1-1.1.2: Manufacturer: Cypress > [ 34.902480] usbdev_probe > [ 34.902681] usbcore: registered new interface driver My USB Device > [ 45.416310] usb 1-1.1.2: USB disconnect, device number 5 > [ 45.416655] usbdev_disconnect > [ 61.326035] usb 1-1.1.2: new high-speed USB device number 6 using dwc_otg > [ 61.457674] usb 1-1.1.2: New USB device found, idVendor=04b4, > idProduct=00f1, bcdDevice= 0.00 > [ 61.457692] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, > SerialNumber=0 > [ 61.457706] usb 1-1.1.2: Product: FX3 > [ 61.457720] usb 1-1.1.2: Manufacturer: Cypress That is odd, sorry, don't know what to suggest. greg k-h ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: some u-boot mailing list
Hi all! On 15/10/2020 07:38, Tomek The Messenger wrote: [...] > Does anybody know some u-boot mailing list like here for linux, but for > u-boot. Is someone subscribed maybe somewhere? I have question about what > might be a potential rootcause of synchronous abort which I get when > executing "i2c dev 1" in u-boot shell. https://www.denx.de/wiki/U-Boot/Contacts And no, I'm not subscribed ... MfG, Bernd -- There is no cloud, just other people computers. -- https://static.fsf.org/nosvn/stickers/thereisnocloud.svg pEpkey.asc Description: application/pgp-keys ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: USB Question about devices being reconnected to the host
On 10/15/20 1:30 PM, Greg KH wrote: On Thu, Oct 15, 2020 at 01:17:45PM +0100, Lucas Tanure wrote: Hi, I'm learning about USB drivers and I would like to know about disconnecting and reconnecting usb devices. I can see my probe function being called and also the disconnect function. But if I reconnect the device there is no call from the kernel to notify my driver about the device being reconnected. That's not good, your driver should be told this. I can also see that the module for my driver was not unloaded, so I dont understand the life cycle of a USB device. Modules are never auto-unloaded. If the module is not unloaded at disconnection and re-loaded for a new device being connected, how can the driver know the device is there after a disconnection? The probe function should be called, are you sure it isn't? I re-did the test couple more times and I can see now the probe function being called. Thanks Thanks Lucas This is my dmesg for the driver at the end of this email: [ 34.706041] usb 1-1.1.2: new high-speed USB device number 5 using dwc_otg [ 34.837647] usb 1-1.1.2: New USB device found, idVendor=04b4, idProduct=00f1, bcdDevice= 0.00 [ 34.837666] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 34.837679] usb 1-1.1.2: Product: FX3 [ 34.837693] usb 1-1.1.2: Manufacturer: Cypress [ 34.902480] usbdev_probe [ 34.902681] usbcore: registered new interface driver My USB Device [ 45.416310] usb 1-1.1.2: USB disconnect, device number 5 [ 45.416655] usbdev_disconnect [ 61.326035] usb 1-1.1.2: new high-speed USB device number 6 using dwc_otg [ 61.457674] usb 1-1.1.2: New USB device found, idVendor=04b4, idProduct=00f1, bcdDevice= 0.00 [ 61.457692] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 61.457706] usb 1-1.1.2: Product: FX3 [ 61.457720] usb 1-1.1.2: Manufacturer: Cypress That is odd, sorry, don't know what to suggest. greg k-h ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Oops stack trace missing function addresses
Hi everyone, I wrote a small kernel module where I trigger a page fault by writing to an invalid memory address. This causes an Oops that prints the associated Stack Trace, but contrary to what the kernel documentation claims, I get no VA next to each function in the Call Trace: Call Trace: do_one_initcall+0xfc/0x290 ? cache_alloc_debugcheck_after+0x38/0x270 ? rcu_read_lock_sched_held+0x77/0xa0 ? kmem_cache_alloc_trace+0x2b6/0x330 do_init_module+0x4b/0x1b6 load_module+0x2140/0x24c0 ? find_held_lock+0x2d/0xa0 sys_init_module+0xdd/0x100 do_int80_syscall_32+0x73/0x170 entry_INT80_32+0xcf/0xcf This looks very much unlike what I see in https://www.kernel.org/doc/html/v4.11/admin-guide/bug-hunting.html I was wondering maybe the reason is that I didn't compile the kernel with the right debug options, but a quick glance at the .config file reveals they all seem to be there: CONFIG_DEBUG_INFO=y CONFIG_STACKTRACE=y CONFIG_DEBUG_BUGVERBOSE=y Cheers, Adrian ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Oops stack trace missing function addresses
On Thu, 15 Oct 2020 18:34:08 +0100, Adrian Larumbe said: > claims, I get no VA next to each function in the Call Trace: > > Call Trace: > do_one_initcall+0xfc/0x290 > ? cache_alloc_debugcheck_after+0x38/0x270 > ? rcu_read_lock_sched_held+0x77/0xa0 > ? kmem_cache_alloc_trace+0x2b6/0x330 > do_init_module+0x4b/0x1b6 > load_module+0x2140/0x24c0 OK, I'll bite. You *are* getting the function name and offset, what additional knowledge do you get from knowing the VA? What architecture is this on? Stack unwinding is architecture-dependent, so it may just be the unwinder for that arch doesn't output the virtual address. pgpJ89sdbw6JQ.pgp Description: PGP signature ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
