Posts
109
Following
28
Followers
25
A maintainer of Linux FireWire subsystem and ALSA firewire stack.
http://ieee1394.docs.kernel.org/
https://github.com/takaswie/linux-firewire-dkms/
takaswie

Takashi Sakamoto (坂本 貴史)

Edited 1 year ago
Need sponsors:

* #1080372 RFS: libhinoko/1.0.3-1 [ITP] -- I/O library for IEEE 1394 isochronous communication
** https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080372
** https://mentors.debian.net/package/libhinoko/
* #1081809 RFS: libhitaki/0.2.1-3 [ITP] -- Library to operate ALSA HwDep device for ALSA firewire stack
** https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081809
** https://mentors.debian.net/package/libhitaki/
* #1081810 RFS: linux-firewire-utils/0.5.1-2 [ITP] -- Linux FireWire utilities
** https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081810
** https://mentors.debian.net/package/linux-firewire-utils/
0
1
1
takaswie

Takashi Sakamoto (坂本 貴史)

Phew.
0
0
0
takaswie

Takashi Sakamoto (坂本 貴史)

Edited 1 year ago
I believe BH workqueue is not necessarily required for the purpose:

[RFT][PATCH 0/5] firewire: use sleepable workqueue to handle 1394 OHCI IT/IR context events
https://lore.kernel.org/lkml/20240901110642.154523-1-o-takashi@sakamocchi.jp/
0
0
0
takaswie

Takashi Sakamoto (坂本 貴史)

Unexpectedly, I can easily replace tasklet with workqueue for 1394 OHCI IR/IT contexts in v6.11 kernel, at least for userspace application. Hm.
0
0
0
takaswie

Takashi Sakamoto (坂本 貴史)

[PATCH] firewire: core: update fw_device outside of device_find_child()

https://lore.kernel.org/lkml/20240820132132.28839-1-o-takashi@sakamocchi.jp/

I believe it reasonable to separate updating from finding here.
0
0
0
takaswie

Takashi Sakamoto (坂本 貴史)

Completed.
0
0
0
takaswie

Takashi Sakamoto (坂本 貴史)

[PATCH 0/5] firewire: core: use XArray to maintain client resources

https://lore.kernel.org/lkml/20240812235210.28458-1-o-takashi@sakamocchi.jp/
0
0
0
takaswie

Takashi Sakamoto (坂本 貴史)

As a first step.
0
0
0
takaswie

Takashi Sakamoto (坂本 貴史)

[PATCH 0/2] firewire: core: use XArray to maintain firewire device nodes:

https://lore.kernel.org/lkml/20240812014251.165492-1-o-takashi@sakamocchi.jp/
0
0
1
takaswie

Takashi Sakamoto (坂本 貴史)

I'm working to replace usage of IDR with XArray. I was a bit puzzled that DEFINE_XARRAY_ALLOC() and xa_init() are not equivalent. In my opinion, the naming scheme of XArray functions should be reconsidered. It easily confuse me.
0
0
0
takaswie

Takashi Sakamoto (坂本 貴史)

Phew.

[PATCH 00/17] firewire: core/ohci: use guard macro for any type of lock primitives
https://lore.kernel.org/lkml/20240804130225.243496-1-o-takashi@sakamocchi.jp/T/#m3f70c1329301dc504d310a8f71c778061868772b
0
0
1
takaswie

Takashi Sakamoto (坂本 貴史)

Oh, the usage of IDR should be replaced with XArray... Since when?
0
0
0
takaswie

Takashi Sakamoto (坂本 貴史)

Edited 1 year ago
Phew
0
0
0
takaswie

Takashi Sakamoto (坂本 貴史)

I'm surprised to see my protocol analyzer operational again.
0
0
0
takaswie

Takashi Sakamoto (坂本 貴史)

Edited 1 year ago
Need some KUnit tests to check serializer/deserializer of data in payload of isochronous packet for various CIP format. However, the current implementation is tight-coupled to low-level hardware operations and procedures for complicated device-dependent protocols. Mmm.
0
0
0
takaswie

Takashi Sakamoto (坂本 貴史)

Edited 1 year ago
Posted: [GIT PULL] firewire updates for v6.11
https://lore.kernel.org/linux-kernel/20240720084730.GA59546@workstation.local/T/#u

There are many line changes for FireWire subsystem, while there is no
functional change for practical use. The most of changes are for code
refactoring, some KUnit tests to added helper functions, and new
tracepoints events for both the core functions and 1394 OHCI driver.

The tracepoints events now cover the verbose logging enabled by debug
parameter of firewire-ohci kernel module. The parameter would be removed
in any future timing, thus it is now deprecated.
0
0
0
takaswie

Takashi Sakamoto (坂本 貴史)

Hm. I'm investigating to replace the local implementation to maintain blocks in the allocated memory region mapped for DMA purpose with common dma_pool. However, it does not allows to pick up an arbitrary count of blocks at once for continuous memory region. It just connect returned block to the tail of local list, and has no mechanism to keep maintained blocks as continuous.
Typically, this kind of framework requires mechanism to suppress fragmentation, but it has nothing. I prefer its simplicity, but a bit inconvenient for my purpose...
0
0
0
takaswie

Takashi Sakamoto (坂本 貴史)

Being straightforward is not necessarily more adequate than being simple.
0
0
0
takaswie

Takashi Sakamoto (坂本 貴史)

As I said.
0
0
1
takaswie
repeated
lina@vt.social

Hoshino Lina (星乃リナ) 🩵 3D Yuri Wedding 2026!!!

Figuring out how to represent this device's mixer controls in ALSA is pain peko...

1
1
0
Show older
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: