From: Ayush Singh <ayushdevel1325@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: Enable UART after driver removal without reboot
Date: Fri, 18 Aug 2023 18:59:42 +0530 [thread overview]
Message-ID: <29a11034-a09d-c26f-6580-c2cd605c278b@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1040 bytes --]
Hello everyone.
I have a Linux Serdev driver [1] that uses a specific UART. To actually
access the UART directly (`/dev/ttyS4`), I have to enable a device tree
[2] and reboot the device. I was wondering if there was a better way to
go about it.
Is it possible to disable bcfserial (thereby enabling `/dev/ttyS4`) when
the driver is removed (using rmmod)? I need access to `/dev/ttyS4` to
flash new firmware to BeaglePlay CC1352 using bsl [3]. Having to restart
everytime I or anyone else wants to update firmware is not great, while
developing.
I am looking for a cycle like this: `rmmod driver` -> `flash firmware`
-> `modprobe driver`.
Ayush Singh
[1]:
https://git.beagleboard.org/gsoc/greybus/beagleplay-greybus-driver/-/tree/develop
[2]:
https://git.beagleboard.org/beagleboard/linux/-/blob/v5.10.168-ti-arm64-r108/arch/arm64/boot/dts/ti/overlays/k3-am625-beagleplay-bcfserial-no-firmware.dts
[3]:
https://git.beagleboard.org/beagleconnect/zephyr/zephyr/-/blob/sdk-next/boards/arm/beagle_play_cc1352/cc2538-bsl.py
[-- Attachment #1.2: Type: text/html, Size: 1929 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
reply other threads:[~2023-08-18 13:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=29a11034-a09d-c26f-6580-c2cd605c278b@gmail.com \
--to=ayushdevel1325@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).