All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@kaod.org>
To: Alastair D'Silva <alastair@au1.ibm.com>, Joel Stanley <joel@jms.id.au>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: [PATCH 3/3] Add a unit test for RX8900 RTC (time functionality only)
Date: Mon, 31 Oct 2016 07:49:11 +0100	[thread overview]
Message-ID: <3b4e8258-d39c-b158-38a9-972d1917c8be@kaod.org> (raw)
In-Reply-To: <1477542574.2176.90.camel@au1.ibm.com>

On 10/27/2016 06:29 AM, Alastair D'Silva wrote:
> On Thu, 2016-10-27 at 14:51 +1030, Joel Stanley wrote:
>>> -         * This I2C device doesn't exist on the real board.
>>> +         * These I2C devices doesn't exist on the real board.
>>>           * We add it here (only on qtest usage) to be able to do a
>>> bit
>>>           * of simple qtest. See "make check" for details.
>>>           */
>>> -        i2c_create_slave((I2CBus *)qdev_get_child_bus(DEVICE(&s-
>>>> soc.i2c[0]),
>>> -                                                      "i2c"),
>>> -                         "ds1338", 0x68);
>>> +        I2CBus *i2c = (I2CBus *)qdev_get_child_bus(DEVICE(&s-
>>>> soc.i2c[0]),
>>> +                "i2c");
>>> +        i2c_create_slave(i2c, "ds1338", 0x68);
>>> +        i2c_create_slave(i2c, "rx8900", 0x32);
>>
>> I'm not sure how upstream will take this.
>>
>> Is there a reason you didn't add them to an aspeed board instead?
>>
> 
> We are currently missing the *_i2c_create and the associated
> send/receive callbacks required to access the i2c bus from the test
> framework. The structure of aspeed_i2c.c was different enough from
> i2c_imx.c & i2c_omap.c that I need more familiarity with the code
> before I could implement it myself.

Could you extend libqos to have these routines ? or you can start an 
aspeed guest which would have the device with your patchset. take a 
look at the m25p80 test.  

Cheers,

C.

  reply	other threads:[~2016-10-31  6:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-27  2:27 [PATCH 0/3] Add QEMU support for the Epson rx8900 RTC alastair
2016-10-27  2:27 ` [PATCH 1/3] Add Epson RX8900 RTC support alastair
2016-10-27  4:19   ` Joel Stanley
2016-10-27  5:03     ` Alastair D'Silva
2016-10-31  6:40       ` Cédric Le Goater
2016-10-27  2:27 ` [PATCH 2/3] Connect an RX8900 RTC to i2c12 of the AST2500 SOC at address 0x32 alastair
2016-10-31  6:41   ` Cédric Le Goater
2016-11-01  4:44     ` Alastair D'Silva
2016-10-27  2:27 ` [PATCH 3/3] Add a unit test for RX8900 RTC (time functionality only) alastair
2016-10-27  4:21   ` Joel Stanley
2016-10-27  4:29     ` Alastair D'Silva
2016-10-31  6:49       ` Cédric Le Goater [this message]
2016-10-27  4:22 ` [PATCH 0/3] Add QEMU support for the Epson rx8900 RTC Joel Stanley
2016-10-27  4:33   ` Alastair D'Silva
2016-10-31  0:22     ` Andrew Jeffery
2016-10-31  6:54 ` Cédric Le Goater

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=3b4e8258-d39c-b158-38a9-972d1917c8be@kaod.org \
    --to=clg@kaod.org \
    --cc=alastair@au1.ibm.com \
    --cc=joel@jms.id.au \
    --cc=openbmc@lists.ozlabs.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.