Message ID | 20241106001835.2725522-1-chris.packham@alliedtelesis.co.nz |
---|---|
Headers | show |
Series | RTL9300 support for reboot and i2c | expand |
Hi Chris, On Wed, Nov 06, 2024 at 01:18:35PM +1300, Chris Packham wrote: > Add support for the I2C controller on the RTL9300 SoC. There are two I2C > controllers in the RTL9300 that are part of the Ethernet switch register > block. Each of these controllers owns a SCL pin (GPIO8 for the fiorst > I2C controller, GPIO17 for the second). There are 8 possible SDA pins > (GPIO9-16) that can be assigned to either I2C controller. This > relationship is represented in the device tree with a child node for > each SDA line in use. > > This is based on the openwrt implementation[1] but has been > significantly modified > > [1] - https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=target/linux/realtek/files-5.15/drivers/i2c/busses/i2c-rtl9300.c > > Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz> > Reviewed-by: Andi Shyti <andi.shyti@kernel.org> Thanks for following up with v9. I think nothing prevents us from already merging this 4/4 patch, right? Andi
On 6/11/24 22:57, Andi Shyti wrote: > Hi Chris, > > On Wed, Nov 06, 2024 at 01:18:35PM +1300, Chris Packham wrote: >> Add support for the I2C controller on the RTL9300 SoC. There are two I2C >> controllers in the RTL9300 that are part of the Ethernet switch register >> block. Each of these controllers owns a SCL pin (GPIO8 for the fiorst >> I2C controller, GPIO17 for the second). There are 8 possible SDA pins >> (GPIO9-16) that can be assigned to either I2C controller. This >> relationship is represented in the device tree with a child node for >> each SDA line in use. >> >> This is based on the openwrt implementation[1] but has been >> significantly modified >> >> [1] - https://scanmail.trustwave.com/?c=20988&d=pL2r5zHAPsW8d92uECdR2T8Eh4fYX_ZwrCyklfTCzQ&u=https%3a%2f%2fgit%2eopenwrt%2eorg%2f%3fp%3dopenwrt%2fopenwrt%2egit%3ba%3dblob%3bf%3dtarget%2flinux%2frealtek%2ffiles-5%2e15%2fdrivers%2fi2c%2fbusses%2fi2c-rtl9300%2ec >> >> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz> >> Reviewed-by: Andi Shyti <andi.shyti@kernel.org> > Thanks for following up with v9. I think nothing prevents us from > already merging this 4/4 patch, right? > From my end yes it's all good to go. Lee's just applied the mfd binding. The only thing outstanding are the mips dts changes. I'll wait for a bit and chase those up. Hopefully they can make it in the 6.13 window but it's not the end of the world if they don't.
Hi Chris, On Thu, Nov 07, 2024 at 08:47:42AM +1300, Chris Packham wrote: > On 6/11/24 22:57, Andi Shyti wrote: > > On Wed, Nov 06, 2024 at 01:18:35PM +1300, Chris Packham wrote: > > > Add support for the I2C controller on the RTL9300 SoC. There are two I2C > > > controllers in the RTL9300 that are part of the Ethernet switch register > > > block. Each of these controllers owns a SCL pin (GPIO8 for the fiorst > > > I2C controller, GPIO17 for the second). There are 8 possible SDA pins > > > (GPIO9-16) that can be assigned to either I2C controller. This > > > relationship is represented in the device tree with a child node for > > > each SDA line in use. > > > > > > This is based on the openwrt implementation[1] but has been > > > significantly modified > > > > > > [1] - https://scanmail.trustwave.com/?c=20988&d=pL2r5zHAPsW8d92uECdR2T8Eh4fYX_ZwrCyklfTCzQ&u=https%3a%2f%2fgit%2eopenwrt%2eorg%2f%3fp%3dopenwrt%2fopenwrt%2egit%3ba%3dblob%3bf%3dtarget%2flinux%2frealtek%2ffiles-5%2e15%2fdrivers%2fi2c%2fbusses%2fi2c-rtl9300%2ec > > > > > > Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz> > > > Reviewed-by: Andi Shyti <andi.shyti@kernel.org> > > Thanks for following up with v9. I think nothing prevents us from > > already merging this 4/4 patch, right? > > > From my end yes it's all good to go. Lee's just applied the mfd binding. > > The only thing outstanding are the mips dts changes. I'll wait for a bit and > chase those up. Hopefully they can make it in the 6.13 window but it's not > the end of the world if they don't. Cool, I just wanted to confirm. Applied to i2c/i2c-host. Thanks, Andi