From: "Cédric Le Goater" <clg@kaod.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org,
"Markus Armbruster" <armbru@redhat.com>
Cc: <qemu-block@nongnu.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@aj.id.au>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PATCH 0/8] aspeed: I2C fixes, -drive removal (first step)
Date: Fri, 17 Feb 2023 09:26:44 +0100 [thread overview]
Message-ID: <cf4f3bee-a02f-3fc0-f86e-dccbda7a7613@kaod.org> (raw)
In-Reply-To: <01ff80e9-c564-5566-5405-b2ca26dfbf09@linaro.org>
On 2/15/23 11:45, Philippe Mathieu-Daudé wrote:
> On 14/2/23 18:18, Cédric Le Goater wrote:
>> Hello,
>>
>> This series starts with a first set of patches fixing I2C slave mode
>> in the Aspeed I2C controller, a test device and its associated test in
>> avocado.
>>
>> Follow some cleanups which allow the use of block devices instead of
>> drives. So that, instead of specifying :
>>
>> -drive file=./flash-ast2600-evb,format=raw,if=mtd
>> -drive file=./ast2600-evb.pnor,format=raw,if=mtd
>> ...
>>
>> and guessing from the order which bus the device is attached to, we
>> can use :
>>
>> -blockdev node-name=fmc0,driver=file,filename=./bmc.img
>> -device mx66u51235f,bus=ssi.0,drive=fmc0
>> -blockdev node-name=fmc1,driver=file,filename=./bmc-alt.img
>> -device mx66u51235f,bus=ssi.0,drive=fmc1
>> -blockdev node-name=pnor,driver=file,filename=./pnor
>> -device mx66l1g45g,bus=ssi.1,drive=pnor
>> ...
>>
>> It is not perfect, the CS index still depends on the order
>
> Quick thoughts here:
>
> TYPE_SSI_PERIPHERAL devices have one input SSI_GPIO_CS.
>
> TYPE_SSI_BUS could have a "cs-num" property (how many
> CS line associated with this bus) and create an array of
> #cs-num output SSI_GPIO_CS.
>
> TYPE_SSI_PERIPHERAL could have a "cs" (index) property;
> if set, upon ssi_peripheral_realize() when the device is
> plugged on the bus, the GPIO line is wired.
yes. I would like to check first the impact on migration compatibility.
Thanks,
C.
> So we could set the 'cs=' property from CLI:
>
> -blockdev node-name=fmc0,driver=file,filename=./bmc.img
> -device mx66u51235f,bus=ssi.0,cs=1,drive=fmc0
> -blockdev node-name=fmc1,driver=file,filename=./bmc-alt.img
> -device mx66u51235f,bus=ssi.0,cs=0,drive=fmc1
>
>> but it is
>> now possible to run a machine without -drive ...,if=mtd.
>>
>> This lacks the final patch enabling the '-nodefaults' option by not
>> creating the default devices if specified on the command line. It
>> needs some more evaluation of the possible undesired effects.
>> Thanks,
>>
>> C.
>
prev parent reply other threads:[~2023-02-17 8:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 17:18 [PATCH 0/8] aspeed: I2C fixes, -drive removal (first step) Cédric Le Goater
2023-02-14 17:18 ` [PATCH 1/8] m25p80: Improve error when the backend file size does not match the device Cédric Le Goater
2023-02-15 19:52 ` Peter Delevoryas
2023-02-16 8:47 ` Philippe Mathieu-Daudé
2023-02-14 17:18 ` [PATCH 2/8] hw/i2c: only schedule pending master when bus is idle Cédric Le Goater
2023-02-14 17:18 ` [PATCH 3/8] hw/misc: add a toy i2c echo device Cédric Le Goater
2023-02-15 10:55 ` Philippe Mathieu-Daudé
2023-02-15 11:09 ` Cédric Le Goater
2023-02-15 12:26 ` Philippe Mathieu-Daudé
2023-02-17 8:24 ` Cédric Le Goater
2023-02-14 17:18 ` [PATCH 4/8] tests/avocado/machine_aspeed.py: Add I2C slave tests Cédric Le Goater
2023-02-14 17:18 ` [PATCH 5/8] aspeed/smc: Replace SysBus IRQs with GPIO lines Cédric Le Goater
2023-02-15 10:56 ` Philippe Mathieu-Daudé
2023-02-14 17:18 ` [PATCH 6/8] aspeed/smc: Wire CS lines at reset Cédric Le Goater
2023-02-14 17:18 ` [PATCH 7/8] aspeed: Introduce a spi_boot region under the SoC Cédric Le Goater
2023-02-15 11:02 ` Philippe Mathieu-Daudé
2023-03-01 13:27 ` Cédric Le Goater
2023-02-14 17:18 ` [PATCH 8/8] aspeed: Add a boot_rom overlap region in the SoC spi_boot container Cédric Le Goater
2023-02-15 6:38 ` [PATCH 0/8] aspeed: I2C fixes, -drive removal (first step) Markus Armbruster
2023-02-15 8:32 ` Cédric Le Goater
2023-02-15 12:35 ` Markus Armbruster
2023-02-17 8:22 ` Cédric Le Goater
2023-02-15 10:45 ` Philippe Mathieu-Daudé
2023-02-17 8:26 ` Cédric Le Goater [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=cf4f3bee-a02f-3fc0-f86e-dccbda7a7613@kaod.org \
--to=clg@kaod.org \
--cc=andrew@aj.id.au \
--cc=armbru@redhat.com \
--cc=joel@jms.id.au \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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 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).