From: "Takashi Sakamoto" <o-takashi@sakamocchi.jp>
To: "Jiri Slaby" <jirislaby@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] firewire updates for 6.5-rc1
Date: Sun, 01 Oct 2023 14:15:16 +0900 [thread overview]
Message-ID: <0ed4012a-83a7-4849-92c4-87a86e1bbb84@app.fastmail.com> (raw)
In-Reply-To: <a12593c9-9ced-4bb8-b7a5-8247b08d0e0f@kernel.org>
Hi Jiri,
Just now I installed openSUSE Tumbleweed, however I found no issue on my 1394 OHCI
hardware. I would like to ask your current opinion for the issue?
~> uname -r
6.5.4-1-default
~> cat /etc/os-release
NAME="openSUSE Tumbleweed"
# VERSION="20230929"
ID="opensuse-tumbleweed"
ID_LIKE="opensuse suse"
VERSION_ID="20230929"
PRETTY_NAME="openSUSE Tumbleweed"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:tumbleweed:20230929"
BUG_REPORT_URL="https://bugzilla.opensuse.org"
SUPPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org"
DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed"
LOGO="distributor-logo-Tumbleweed"
->sudo lspci -v
...
01:00.0 PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI Bridge [Cheetah Express] (rev 01) (prog-if 00 [Normal decode])
Subsystem: Device 3412:7856
Flags: bus master, fast devsel, latency 0, IOMMU group 8
Memory at fce00000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=01, secondary=02, subordinate=02, sec-latency=32
I/O behind bridge: [disabled] [32-bit]
Memory behind bridge: fcd00000-fcdfffff [size=1M] [32-bit]
Prefetchable memory behind bridge: [disabled] [64-bit]
Capabilities: [50] Power Management version 3
Capabilities: [60] MSI: Enable- Count=1/16 Maskable- 64bit+
Capabilities: [80] Subsystem: Device 3412:7856
Capabilities: [90] Express PCI-Express to PCI/PCI-X Bridge, MSI 00
Capabilities: [100] Advanced Error Reporting
02:00.0 FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express] (rev 01) (prog-if 10 [OHCI])
Subsystem: Device 3412:7856
Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 39, IOMMU group 8
Memory at fcd04000 (32-bit, non-prefetchable) [size=2K]
Memory at fcd00000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [44] Power Management version 3
Kernel driver in use: firewire_ohci
Kernel modules: firewire_ohci
...
$ udevadm info -e
...
P: /devices/pci0000:00/0000:00:01.1/0000:01:00.0
M: 0000:01:00.0
R: 0
U: pci
E: DEVPATH=/devices/pci0000:00/0000:00:01.1/0000:01:00.0
E: SUBSYSTEM=pci
E: PCI_CLASS=60400
E: PCI_ID=104C:823E
E: PCI_SUBSYS_ID=3412:7856
E: PCI_SLOT_NAME=0000:01:00.0
E: MODALIAS=pci:v0000104Cd0000823Esv00003412sd00007856bc06sc04i00
E: USEC_INITIALIZED=11023840
E: ID_PCI_CLASS_FROM_DATABASE=Bridge
E: ID_PCI_SUBCLASS_FROM_DATABASE=PCI bridge
E: ID_PCI_INTERFACE_FROM_DATABASE=Normal decode
E: ID_VENDOR_FROM_DATABASE=Texas Instruments
E: ID_MODEL_FROM_DATABASE=XIO2213A/B/XIO2221 PCI Express to PCI Bridge [Cheetah Express]
E: ID_PATH=pci-0000:01:00.0
E: ID_PATH_TAG=pci-0000_01_00_0
P: /devices/pci0000:00/0000:00:01.1/0000:01:00.0/0000:02:00.0
M: 0000:02:00.0
R: 0
U: pci
V: firewire_ohci
E: DEVPATH=/devices/pci0000:00/0000:00:01.1/0000:01:00.0/0000:02:00.0
E: SUBSYSTEM=pci
E: DRIVER=firewire_ohci
E: PCI_CLASS=C0010
E: PCI_ID=104C:823F
E: PCI_SUBSYS_ID=3412:7856
E: PCI_SLOT_NAME=0000:02:00.0
E: MODALIAS=pci:v0000104Cd0000823Fsv00003412sd00007856bc0Csc00i10
E: USEC_INITIALIZED=11023930
E: ID_PCI_CLASS_FROM_DATABASE=Serial bus controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=FireWire (IEEE 1394)
E: ID_PCI_INTERFACE_FROM_DATABASE=OHCI
E: ID_VENDOR_FROM_DATABASE=Texas Instruments
E: ID_MODEL_FROM_DATABASE=XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express]
E: ID_PATH=pci-0000:02:00.0
E: ID_PATH_TAG=pci-0000_02_00_0
P: /devices/pci0000:00/0000:00:01.1/0000:01:00.0/0000:02:00.0/fw0
M: fw0
R: 0
U: firewire
D: c 244:0
N: fw0
L: 0
E: DEVPATH=/devices/pci0000:00/0000:00:01.1/0000:01:00.0/0000:02:00.0/fw0
E: SUBSYSTEM=firewire
E: DEVNAME=/dev/fw0
E: MAJOR=244
E: MINOR=0
...
When I plugged in my sound device (Tascam Fireone) and load ALSA OXFW driver, it works as expected. It means that both 1394 Asynchronous/Isochronous communications are established as expected.
Regards
Takashi Sakamoto
next prev parent reply other threads:[~2023-10-01 5:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 12:18 Takashi Sakamoto
2023-07-04 18:38 ` pr-tracker-bot
2023-09-26 9:11 ` Jiri Slaby
2023-09-26 14:09 ` Takashi Sakamoto
2023-09-27 5:03 ` Jiri Slaby
2023-10-01 5:15 ` Takashi Sakamoto [this message]
2023-10-02 10:42 ` Jiri Slaby
2023-10-04 0:24 ` Takashi Sakamoto
2023-10-04 8:33 ` Jiri Slaby
2023-10-16 15:56 ` Takashi Sakamoto
2023-10-17 7:36 ` Jiri Slaby
2023-09-27 13:15 ` Linux regression tracking #adding (Thorsten Leemhuis)
2024-01-21 10:04 ` Linux regression tracking #update (Thorsten Leemhuis)
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=0ed4012a-83a7-4849-92c4-87a86e1bbb84@app.fastmail.com \
--to=o-takashi@sakamocchi.jp \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®