Hi Anjana,
Try to enable the USB debug to see if the usbhost_destroy() is called
to unregister the device:
/* Unregister the driver */
uinfo("Unregister driver\n");
usbhost_mkdevname(priv, devname);
unregister_driver(devname);
/* Release the device name used by this connection */
usbhost_freedevno(priv);
You should see the "Unregister driver" printed when you remove your
keyboard. If it is not happening, maybe your USB driver implementation
is not notifying correctly about the disconnect event.
BR,
Alan
On 7/6/20, Anjana <anj...@tataelxsi.co.in.invalid> wrote:
> Hello Team,
>
> We have implemented the USB Host driver for Renesas RX65N target.
>
> We are using the keyboard class driver for testing.
>
> We have observed the issue mentioned below, upon disconnection of USB
> Keyboard
>
> Issue Observed:
>
>
> 1. When the keyboard device is removed, the device node "/dev/kbd", is
> not getting removed from /dev directory.
> 2. Even upon disconnection of USB Keyboard device, the device node still
> exists.
> 3. This issue is observed for keyboard device only. When the mass stoarge
> device is used, this issue is not observed.(Device node for mass storage
> class, is removed correctly upon disconnection)
>
> Has anyone faced similar issue ?
>
> Any inputs to resolve the issue will be helpful
>
>
>
>
> Regards,
>
> Anjana
>
>
> ________________________________
> Disclaimer: This email and any files transmitted with it are confidential
> and intended solely for the use of the individual or entity to whom they are
> addressed. If you are not the intended recipient of this message , or if
> this message has been addressed to you in error, please immediately alert
> the sender by reply email and then delete this message and any attachments.
> If you are not the intended recipient, you are hereby notified that any use,
> dissemination, copying, or storage of this message or its attachments is
> strictly prohibited. Email transmission cannot be guaranteed to be secure or
> error-free, as information could be intercepted, corrupted, lost, destroyed,
> arrive late or incomplete, or contain viruses. The sender, therefore, does
> not accept liability for any errors, omissions or contaminations in the
> contents of this message which might have occurred as a result of email
> transmission. If verification is required, please request for a hard-copy
> version.
> ________________________________
>
