From: Laurent Vivier <laurent@vivier.eu>
To: Pavel Pisa <pisa@cmp.felk.cvut.cz>
Cc: "Thomas Huth" <thuth@redhat.com>,
qemu-trivial@nongnu.org,
"Oliver Hartkopp" <socketcan@hartkopp.net>,
"Jason Wang" <jasowang@redhat.com>,
qemu-devel@nongnu.org, "Ondrej Ille" <ondrej.ille@gmail.com>,
"Jan Charvát" <charvj10@fel.cvut.cz>
Subject: Re: [PATCH] hw/net/can: Add missing fallthrough statements
Date: Tue, 1 Sep 2020 08:42:57 +0200 [thread overview]
Message-ID: <278ac22c-e3f9-cc93-c711-ad420102141f@vivier.eu> (raw)
In-Reply-To: <202007140009.55103.pisa@cmp.felk.cvut.cz>
Le 14/07/2020 à 00:09, Pavel Pisa a écrit :
> Hello Laurent and others,
>
> On Monday 06 of July 2020 18:35:50 Laurent Vivier wrote:
>> Le 30/06/2020 à 09:55, Thomas Huth a écrit :
>>> Add fallthrough annotations to be able to compile the code without
>>> warnings when using -Wimplicit-fallthrough in our CFLAGS. Looking
>>> at the code, it seems like the fallthrough is indeed intended here,
>>> so the comments should be appropriate.
>>>
>>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>>> ---
>>> hw/net/can/can_sja1000.c | 2 ++
>>> 1 file changed, 2 insertions(+)
>>>
>>> diff --git a/hw/net/can/can_sja1000.c b/hw/net/can/can_sja1000.c
>>> index ea915a023a..299932998a 100644
>>> --- a/hw/net/can/can_sja1000.c
>>> +++ b/hw/net/can/can_sja1000.c
>>> @@ -523,6 +523,7 @@ void can_sja_mem_write(CanSJA1000State *s, hwaddr
>>> addr, uint64_t val, break;
>>> case 16: /* RX frame information addr16-28. */
>>> s->status_pel |= (1 << 5); /* Set transmit status. */
>>> + /* fallthrough */
>>> case 17 ... 28:
>>> if (s->mode & 0x01) { /* Reset mode */
>>> if (addr < 24) {
>>> @@ -620,6 +621,7 @@ void can_sja_mem_write(CanSJA1000State *s, hwaddr
>>> addr, uint64_t val, break;
>>> case 10:
>>> s->status_bas |= (1 << 5); /* Set transmit status. */
>>> + /* fallthrough */
>>> case 11 ... 19:
>>> if ((s->control & 0x01) == 0) { /* Operation mode */
>>> s->tx_buff[addr - 10] = val; /* Store to TX buffer
>>> directly. */
>>
>> cc: Pavel Pisa <pisa@cmp.felk.cvut.cz>
>>
>> Reviewed-by: Laurent Vivier <laurent@vivier.eu>
>
> The fallthrough is intentional for sure but I have gone
> through datasheet and checked why the status bit is set
> there and my conclusion is that to mimic real HW the status
> bit should not be set there. In the fact, it should be set
> and immediately (in a future delayed) reset after SJA_CMR
> transmit request write. This would mimic real hardware
> more closely. May it be I send patch in future when more
> of our developed CAN support is added to QEMU. The status
> bit behavior has no influence on actual Linux SJA1000 driver
> anyway.
>
> So for now, I confirm that adding /* fallthrough */ is correct
> step forward.
>
> Reviewed-by: Pavel Pisa <pisa@cmp.felk.cvut.cz>
>
Applied to my trivial-patches branch.
Thanks,
Laurent
prev parent reply other threads:[~2020-09-01 6:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 7:55 [PATCH] hw/net/can: Add missing fallthrough statements Thomas Huth
2020-07-06 16:35 ` Laurent Vivier
2020-07-13 22:09 ` Pavel Pisa
2020-09-01 6:42 ` Laurent Vivier [this message]
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=278ac22c-e3f9-cc93-c711-ad420102141f@vivier.eu \
--to=laurent@vivier.eu \
--cc=charvj10@fel.cvut.cz \
--cc=jasowang@redhat.com \
--cc=ondrej.ille@gmail.com \
--cc=pisa@cmp.felk.cvut.cz \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=socketcan@hartkopp.net \
--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).