Skip to content

drivers: fix the Hs-mode range in I2C Address.check_reserved - #1099

Merged
mattnite merged 1 commit into
ZigEmbeddedGroup:mainfrom
SAY-5:fix-i2c-hs-reserved-range
Oct 29, 2026
Merged

mattnite merged 1 commit into
ZigEmbeddedGroup:mainfrom
SAY-5:fix-i2c-hs-reserved-range

Conversation

@SAY-5

@SAY-5 SAY-5 commented Oct 25, 2026

Copy link
Copy Markdown
Contributor

Fixes #1085

The Hs-mode controller code is 0000 1XX (0x04-0x07), but check_reserved returned HighSpeedMaster for 0x08-0x0F, so ordinary addresses such as 0x0C were refused and the real Hs-mode codes were accepted. The test table had the same wrong range, so it now expects 0x04 and 0x07 to be reserved and 0x08 to be valid.

Signed-off-by: Sai Asish Y <say.apm35@gmail.com>

@Grazfather Grazfather left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good find

@mattnite
mattnite merged commit ab32518 into ZigEmbeddedGroup:main Oct 29, 2026
37 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

drivers: I2C_Device.Address.check_reserved rejects 0x08-0x0F and accepts 0x04-0x07 (HighSpeedMaster range is off by one bit)

3 participants