Re: [PATCH v3 1/2] hw/gpio: add K230 GPIO controller model

Junze Cao <[email protected]>
Newsgroups org.nongnu.qemu-devel,org.nongnu.qemu-riscv
Message-ID <178670395948.644010.10747276999132854035.b4-reply@b4>
On 2026-08-14 17:50:55+08:00, Bin Meng wrote:
> Hi Junze,
> 
> On Fri, Aug 14, 2026 at 5:21 PM Junze Cao <[email protected]> wrote:
> 
> > On 2026-08-14 15:26:41+08:00, Bin Meng wrote:
> >
> > Hi Bin Meng,
> >
> > Thanks for the detailed review.
> > Regarding the suggestion to abstract this into a generic Synopsys DesignWare APB GPIO model, I have a question: do you know of any other QEMU SoCs that use this IP and would benefit from a shared model?
> > If there is no immediate second user, I wonder whether it might be premature to generalize now, especially while we still need to complete the K230-specific behavior.
> 
> There is no other immediate second user as far as I know. But Synopsys
> DesignWare IP is not like others, and it's commonly seen on many SoCs.
> 
> For RISC-V, I can see Eswin EIC7700, Sophgo CV1800B (Milk-V Duo),
> Sophgo SG2042 / SG2044 and T-Head TH1520 (Lichee Pi 4A) all use the
> same Synopsys GPIO IP, and they are all good candidate of QEMU models
> in the future.
> 
> What K230-specific behavior are you concerned about?
> 
> Regards,
> Bin

Hi Bin,

Thank you for the clarification and for pointing out the other potential users of this IP.

After reconsidering the issue, I realize that my earlier concerns about K230-specific behavior were unfounded. 
I agree that abstracting this into a generic Synopsys DesignWare APB GPIO model would be a worthwhile approach, and I support moving forward in that direction.

Thank you again for your guidance.

Best regards,
Junze
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.