From: Julia Suvorova <jusual@mail.ru>
To: Thomas Huth <thuth@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Laurent Vivier <lvivier@redhat.com>,
Joel Stanley <joel@jms.id.au>,
Peter Maydell <peter.maydell@linaro.org>,
jim@groklearning.com, qemu-arm@nongnu.org,
contrib@steffen-goertz.de
Subject: Re: [Qemu-devel] [PATCH v2 2/2] tests/microbit-test: add TWI stub device test
Date: Thu, 10 Jan 2019 13:11:05 +0300 [thread overview]
Message-ID: <5cc00012-1929-22a0-cbf8-14573b083ae7@mail.ru> (raw)
In-Reply-To: <cd32de08-afd0-4b8b-a10a-99e1d88d1755@redhat.com>
On 10.01.2019 12:48, Thomas Huth wrote:
> On 2019-01-10 10:40, Stefan Hajnoczi wrote:
>> This test verifies that we read back the expected I2C WHO_AM_I register
>> values for the accelerometer/magnetometer.
>>
>> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
>> ---
>> tests/microbit-test.c | 44 +++++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 44 insertions(+)
>>
>> diff --git a/tests/microbit-test.c b/tests/microbit-test.c
>> index 0c125535f6..dcdc0cd41a 100644
>> --- a/tests/microbit-test.c
>> +++ b/tests/microbit-test.c
>> @@ -21,6 +21,49 @@
>> #include "hw/arm/nrf51.h"
>> #include "hw/gpio/nrf51_gpio.h"
>> #include "hw/timer/nrf51_timer.h"
>> +#include "hw/i2c/microbit_i2c.h"
>> +
>> +/* Read a byte from I2C device at @addr from register @reg */
>> +static uint32_t i2c_read_byte(uint32_t addr, uint32_t reg)
>> +{
>> + uint32_t val;
>> +
>> + writel(NRF51_TWI_BASE + NRF51_TWI_REG_ADDRESS, addr);
>> + writel(NRF51_TWI_BASE + NRF51_TWI_TASK_STARTTX, 1);
>> + writel(NRF51_TWI_BASE + NRF51_TWI_REG_TXD, reg);
>> + val = readl(NRF51_TWI_BASE + NRF51_TWI_EVENT_TXDSENT);
>> + g_assert_cmpuint(val, ==, 1);
>> + writel(NRF51_TWI_BASE + NRF51_TWI_TASK_STOP, 1);
>> +
>> + writel(NRF51_TWI_BASE + NRF51_TWI_TASK_STARTRX, 1);
>> + val = readl(NRF51_TWI_BASE + NRF51_TWI_EVENT_RXDREADY);
>> + g_assert_cmpuint(val, ==, 1);
>> + val = readl(NRF51_TWI_BASE + NRF51_TWI_REG_RXD);
>> + writel(NRF51_TWI_BASE + NRF51_TWI_TASK_STOP, 1);
>
> Any chance that you could use qemu_writel() right from the start here?
> That will make it easier to finally get rid of global_qtest one day...
I'll send a patch soon to fix it.
But this test can be merged without corrections.
Best regards, Julia Suvorova.
next prev parent reply other threads:[~2019-01-10 10:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 9:40 [Qemu-devel] [PATCH v2 0/2] arm: Stub out NRF51 TWI magnetometer/accelerometer detection Stefan Hajnoczi
2019-01-10 9:40 ` [Qemu-devel] [PATCH v2 1/2] " Stefan Hajnoczi
2019-01-18 13:57 ` Peter Maydell
2019-01-20 14:10 ` Stefan Hajnoczi
2019-01-10 9:40 ` [Qemu-devel] [PATCH v2 2/2] tests/microbit-test: add TWI stub device test Stefan Hajnoczi
2019-01-10 9:48 ` Thomas Huth
2019-01-10 10:11 ` Julia Suvorova [this message]
2019-01-11 6:36 ` Stefan Hajnoczi
2019-01-21 16:21 ` [Qemu-devel] [PATCH v2 0/2] arm: Stub out NRF51 TWI magnetometer/accelerometer detection Peter Maydell
2019-01-22 9:26 ` Stefan Hajnoczi
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=5cc00012-1929-22a0-cbf8-14573b083ae7@mail.ru \
--to=jusual@mail.ru \
--cc=contrib@steffen-goertz.de \
--cc=jim@groklearning.com \
--cc=joel@jms.id.au \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.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).