devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Troy Mitchell <troymitchell988@gmail.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: andi.shyti@kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org, krzk+dt@kernel.org,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
	robh@kernel.org
Subject: Re: [PATCH v1 2/2] i2c: spacemit: add support for SpacemiT K1 SoC
Date: Wed, 16 Oct 2024 10:26:29 +0800	[thread overview]
Message-ID: <6015d35d-6d91-4ac1-8ebf-4f79b304370f@gmail.com> (raw)
In-Reply-To: <Zw4zPOXSJIWEMd2Y@shikoro>



On 2024/10/15 17:17, Wolfram Sang wrote:
> 
>> +/* spacemit i2c registers */
>> +#define ICR          0x0		/* Control Register */
>> +#define ISR          0x4		/* Status Register */
>> +#define ISAR         0x8		/* Slave Address Register */
>> +#define IDBR         0xc		/* Data Buffer Register */
>> +#define ILCR         0x10		/* Load Count Register */
>> +#define IWCR         0x14		/* Wait Count Register */
>> +#define IRST_CYC     0x18		/* Bus reset cycle counter */
>> +#define IBMR         0x1c		/* Bus monitor register */
> 
> These registers look a lot like the ones for i2c-pxa. Can the pxa driver
> maybe be re-used for your I2C core?
> 
Only a small number of bit definitions in the registers are the same [1].
Even if the logic is roughly the same. it still takes a lot of work,
and i2c-pxa cannot easily add the fifo and dma functions that k1 has.
Just my opinion, I don't think it's worth it.
of course, if you think that multiplexing i2c-pxa is a better decision.
I'd be happy to adopt it

Link: https://developer.spacemit.com/documentation?token=Rn9Kw3iFHirAMgkIpTAcV2Arnkf#part2065 [1]

  reply	other threads:[~2024-10-16  2:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-15  7:51 [PATCH v1 0/2] riscv: spacemit: add i2c support to K1 SoC Troy Mitchell
2024-10-15  7:51 ` [PATCH v1 1/2] dt-bindings: i2c: spacemit: add support for " Troy Mitchell
2024-10-15  8:02   ` Krzysztof Kozlowski
2024-10-15 16:47     ` Conor Dooley
2024-10-16  2:45     ` Troy Mitchell
2024-10-16  7:44       ` Krzysztof Kozlowski
2024-10-15  9:22   ` Rob Herring (Arm)
2024-10-15  7:51 ` [PATCH v1 2/2] i2c: spacemit: add support for SpacemiT " Troy Mitchell
2024-10-15  8:08   ` Krzysztof Kozlowski
2024-10-15  9:21     ` Wolfram Sang
2024-10-18  5:17     ` Troy Mitchell
2024-10-18  6:05       ` Krzysztof Kozlowski
2024-10-18  8:33         ` Troy Mitchell
2024-10-18  8:39           ` Krzysztof Kozlowski
2024-10-15  9:17   ` Wolfram Sang
2024-10-16  2:26     ` Troy Mitchell [this message]
2024-10-16  7:06       ` Wolfram Sang
2024-10-16  9:39   ` Uwe Kleine-König
2024-10-21  7:22   ` Dan Carpenter

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=6015d35d-6d91-4ac1-8ebf-4f79b304370f@gmail.com \
    --to=troymitchell988@gmail.com \
    --cc=andi.shyti@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=wsa+renesas@sang-engineering.com \
    /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;
as well as URLs for NNTP newsgroup(s).