qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Titus Rwantare <titusr@google.com>
To: Peter Delevoryas <peter@pjd.dev>
Cc: qemu-devel@nongnu.org, qemu-arm@nongnu.org, patrick@stwcx.xyz,
	 iwona.winiarska@intel.com, tmaimon77@gmail.com,
	quic_jaehyoo@quicinc.com,  Hao Wu <wuhaotsh@google.com>
Subject: Re: [RFC PATCH 3/3] hw/peci: add support for EndPointConfig reads
Date: Tue, 13 Sep 2022 11:21:23 -0700	[thread overview]
Message-ID: <CAMvPwGoB9jm_mF0bkFBXmHKH2oxbw3N7Z_QgNqs7F=Bktmnu1w@mail.gmail.com> (raw)
In-Reply-To: <YxuYehCwKw/CmWhN@pdel-fedora-MJ0HJWH9>

On Fri, 9 Sept 2022 at 12:48, Peter Delevoryas <peter@pjd.dev> wrote:
>
> On Tue, Sep 06, 2022 at 10:05:52PM +0000, Titus Rwantare wrote:
> > Signed-off-by: Titus Rwantare <titusr@google.com>
> > Reviewed-by: Hao Wu <wuhaotsh@google.com>
> > ---
...
> > +++ b/include/hw/peci/peci.h
> > @@ -112,6 +112,26 @@ typedef struct PECITempTarget {
> >      uint8_t tjmax;
> >  } PECITempTarget;
> >
> > +typedef enum PECIEndPtType {
> > +    LOCAL_PCI_CFG = 3,
> > +    PCI_CFG,
> > +    MMIO_BDF,
> > +} PECIEndPtType;
> > +
> > +typedef struct __attribute__ ((__packed__)) {
> > +    PECIEndPtType msg_type;
> > +    uint8_t addr_type;
> > +    uint8_t bus;
> > +    uint8_t dev;
> > +    uint8_t func;
> > +    uint16_t reg;
> > +} PECIEndPtHeader;
> > +
> > +typedef struct {
> > +    PECIEndPtHeader hdr;
> > +    uint32_t data;
> > +} PECIEndPtConfig;
>
> I noticed the summary is "hw/peci: add support for EndPointConfig reads"
> but type definitions here use "EndPt", maybe they should be
> "PECIEndPoint*"? I don't think extending to Point is too long.

Fair, fixed in v2.


Titus


  reply	other threads:[~2022-09-13 18:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-06 22:05 [RFC PATCH 0/3] Initial PECI bus support Titus Rwantare
2022-09-06 22:05 ` [RFC PATCH 1/3] hw/peci: add initial support for PECI Titus Rwantare
2022-09-09 19:58   ` Peter Delevoryas
2022-09-13 18:21     ` Titus Rwantare
2022-09-13 18:28       ` Peter Delevoryas
2022-09-06 22:05 ` [RFC PATCH 2/3] hw/peci: add PECI support for NPCM7xx BMCs Titus Rwantare
2022-09-09 20:10   ` Peter Delevoryas
2022-09-06 22:05 ` [RFC PATCH 3/3] hw/peci: add support for EndPointConfig reads Titus Rwantare
2022-09-09 19:48   ` Peter Delevoryas
2022-09-13 18:21     ` Titus Rwantare [this message]
2022-09-09 19:54 ` [RFC PATCH 0/3] Initial PECI bus support Peter Delevoryas
2022-09-13 18:20   ` Titus Rwantare
2022-09-13 18:27     ` Peter Delevoryas

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='CAMvPwGoB9jm_mF0bkFBXmHKH2oxbw3N7Z_QgNqs7F=Bktmnu1w@mail.gmail.com' \
    --to=titusr@google.com \
    --cc=iwona.winiarska@intel.com \
    --cc=patrick@stwcx.xyz \
    --cc=peter@pjd.dev \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quic_jaehyoo@quicinc.com \
    --cc=tmaimon77@gmail.com \
    --cc=wuhaotsh@google.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).