From: Andrew Lunn <andrew@lunn.ch>
To: FUJITA Tomonori <fujita.tomonori@gmail.com>
Cc: netdev@vger.kernel.org, rust-for-linux@vger.kernel.org,
tmgross@umich.edu, miguel.ojeda.sandonis@gmail.com,
benno.lossin@proton.me, aliceryhl@google.com
Subject: Re: [PATCH net-next v3 6/6] net: phy: add Applied Micro QT2025 PHY driver
Date: Fri, 16 Aug 2024 03:45:09 +0200 [thread overview]
Message-ID: <0675cff9-5502-43e4-87ee-97d2e35d72da@lunn.ch> (raw)
In-Reply-To: <20240804233835.223460-7-fujita.tomonori@gmail.com>
> +#[vtable]
> +impl Driver for PhyQT2025 {
> + const NAME: &'static CStr = c_str!("QT2025 10Gpbs SFP+");
> + const PHY_DEVICE_ID: phy::DeviceId = phy::DeviceId::new_with_exact_mask(0x0043A400);
> +
> + fn probe(dev: &mut phy::Device) -> Result<()> {
> + // The hardware is configurable?
> + let hw_id = dev.read(C45::new(Mmd::PMAPMD, 0xd001))?;
> + if (hw_id >> 8) & 0xff != 0xb3 {
> + return Ok(());
> + }
I don't understand this bit of code. At a guess, if the upper bytes of
that register is not 0xb3, the firmware has already been loaded into
the device?
> +
> + // The 8051 will remain in the reset state.
> + dev.write(C45::new(Mmd::PMAPMD, 0xC300), 0x0000)?;
> + // Configure the 8051 clock frequency.
> + dev.write(C45::new(Mmd::PMAPMD, 0xC302), 0x0004)?;
> + // Non loopback mode.
> + dev.write(C45::new(Mmd::PMAPMD, 0xC319), 0x0038)?;
> + // Global control bit to select between LAN and WAN (WIS) mode.
> + dev.write(C45::new(Mmd::PMAPMD, 0xC31A), 0x0098)?;
> + dev.write(C45::new(Mmd::PCS, 0x0026), 0x0E00)?;
> + dev.write(C45::new(Mmd::PCS, 0x0027), 0x0893)?;
> + dev.write(C45::new(Mmd::PCS, 0x0028), 0xA528)?;
> + dev.write(C45::new(Mmd::PCS, 0x0029), 0x0003)?;
802.3 says:
3.38 through 3.4110/25GBASE-R PCS test pattern seed B ????
> + // Configure transmit and recovered clock.
> + dev.write(C45::new(Mmd::PMAPMD, 0xC30A), 0x06E1)?;
> + // The 8051 will finish the reset state.
> + dev.write(C45::new(Mmd::PMAPMD, 0xC300), 0x0002)?;
> + // The 8051 will start running from the boot ROM.
> + dev.write(C45::new(Mmd::PCS, 0xE854), 0x00C0)?;
> +
> + let fw = Firmware::request(c_str!("qt2025-2.0.3.3.fw"), dev.as_ref())?;
> + if fw.data().len() > SZ_16K + SZ_8K {
> + return Err(code::EFBIG);
> + }
> +
> + // The 24kB of program memory space is accessible by MDIO.
> + // The first 16kB of memory is located in the address range 3.8000h - 3.BFFFh.
> + // The next 8kB of memory is located at 4.8000h - 4.9FFFh.
> + let mut j = SZ_32K;
> + for (i, val) in fw.data().iter().enumerate() {
> + if i == SZ_16K {
> + j = SZ_32K;
> + }
> +
> + let mmd = if i < SZ_16K { Mmd::PCS } else { Mmd::PHYXS };
> + dev.write(
> + C45::new(mmd, j as u16),
> + <u8 as Into<u16>>::into(*val).to_le(),
This is well past my level of Rust. I assume fw.data is a collection
of bytes, and you enumerate it as bytes. A byte has no endiannes, so
why do you need to convert it to little endian?
Andrew
next prev parent reply other threads:[~2024-08-16 1:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-04 23:38 [PATCH net-next v3 0/6] net: phy: add Applied Micro QT2025 PHY driver FUJITA Tomonori
2024-08-04 23:38 ` [PATCH net-next v3 1/6] rust: sizes: add commonly used constants FUJITA Tomonori
2024-08-16 0:37 ` Andrew Lunn
2024-08-16 5:21 ` FUJITA Tomonori
2024-08-04 23:38 ` [PATCH net-next v3 2/6] rust: net::phy support probe callback FUJITA Tomonori
2024-08-16 0:40 ` Andrew Lunn
2024-08-16 5:21 ` FUJITA Tomonori
2024-08-04 23:38 ` [PATCH net-next v3 3/6] rust: net::phy implement AsRef<kernel::device::Device> trait FUJITA Tomonori
2024-08-16 0:41 ` Andrew Lunn
2024-08-04 23:38 ` [PATCH net-next v3 4/6] rust: net::phy unified read/write API for C22 and C45 registers FUJITA Tomonori
2024-08-16 1:09 ` Andrew Lunn
2024-08-16 5:27 ` FUJITA Tomonori
2024-08-04 23:38 ` [PATCH net-next v3 5/6] rust: net::phy unified genphy_read_status function " FUJITA Tomonori
2024-08-16 1:19 ` Andrew Lunn
2024-08-16 5:30 ` FUJITA Tomonori
2024-08-16 20:41 ` Andrew Lunn
2024-08-04 23:38 ` [PATCH net-next v3 6/6] net: phy: add Applied Micro QT2025 PHY driver FUJITA Tomonori
2024-08-16 1:45 ` Andrew Lunn [this message]
2024-08-16 6:17 ` FUJITA Tomonori
2024-08-16 20:47 ` Andrew Lunn
2024-08-17 4:50 ` FUJITA Tomonori
2024-08-05 1:10 ` [PATCH net-next v3 0/6] " Andrew Lunn
2024-08-14 2:57 ` FUJITA Tomonori
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=0675cff9-5502-43e4-87ee-97d2e35d72da@lunn.ch \
--to=andrew@lunn.ch \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=fujita.tomonori@gmail.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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