On 9/3/23 22:48, Dario Binacchi wrote:
> commit 011644249686f2675e142519cd59e81e04cfc231 Linux upstream.
>
> Add pin configurations for using CAN controller on stm32f7.
>
> Signed-off-by: Dario Binacchi
> Link:
>
Hi Dario
On 9/3/23 22:48, Dario Binacchi wrote:
> commit 8f3ef556f8e1a670895f59ef3f01e4e26edd63e3 Linux upstream.
>
> Add binding definition for CAN3 peripheral.
>
> Signed-off-by: Dario Binacchi
> Link:
> https://lore.kernel.org/r/20230423172528.1398158-2-dario.binac...@amarulasolutions.com
These 2 are only used in drivers/block/blkmap.c.
Signed-off-by: Bin Meng
---
drivers/block/blkmap.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/block/blkmap.c b/drivers/block/blkmap.c
index 409aa46de2..f6acfa8927 100644
--- a/drivers/block/blkmap.c
+++
Since we are emulating a block device, its size should be multiple
of the configured block size.
Signed-off-by: Bin Meng
---
drivers/block/host_dev.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/block/host_dev.c b/drivers/block/host_dev.c
index 0b43f80a86..30c7415793 100644
They are only used in drivers/block/host_dev.c.
Signed-off-by: Bin Meng
---
drivers/block/host_dev.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/block/host_dev.c b/drivers/block/host_dev.c
index 31c7814054..0b43f80a86 100644
--- a/drivers/block/host_dev.c
Allow optionally set the logical block size of the host device to
bind in the "host bind" command. If not given, defaults to 512.
Signed-off-by: Bin Meng
---
cmd/host.c | 16 +---
drivers/block/host-uclass.c | 15 ---
include/sandbox_host.h | 7
At present the host bind command does not require filename to be
provided. When it is not given NULL is passed to the host device
driver, which ends up failure afterwards.
Change to mandate the filename so that it is useful.
Signed-off-by: Bin Meng
---
cmd/host.c | 6 +++---
1 file changed, 3
Avoid using the magic number 512 directly.
Signed-off-by: Bin Meng
---
common/usb_storage.c | 4 ++--
drivers/ata/dwc_ahsata.c | 3 ++-
drivers/ata/fsl_sata.c | 3 ++-
drivers/ata/sata_mv.c| 3 ++-
drivers/ata/sata_sil.c | 3 ++-
drivers/block/blkmap.c | 2 +-
At present on Sandbox when binding to a host backing file, the host
block device is created with a hard-coded 512 bytes block size.
Such assumption works for most cases, but for situation that with a raw
image file dump from a pre-formatted GPT partitioned disk image from a
4KiB block size
On 9/26/23 09:53, Leo Liang wrote:
Hi Heinrich,
On Sat, Sep 23, 2023 at 01:35:26AM +0200, Heinrich Schuchardt wrote:
Most boards don't enable the pre-console buffer. So we will not see any
early messages. OpenSBI 1.3 provides us with the debug console extension
that can fill this gap.
For
On Mon, Sep 25, 2023 at 05:24:52PM +0800, Randolph wrote:
> Unify the memory layout for u-boot SPL mode
> Add "CONFIG_SPL_OPENSBI_SCRATCH_OPTIONS"
>
> Signed-off-by: Randolph
> ---
> configs/ae350_rv32_spl_defconfig | 7 ---
> configs/ae350_rv32_spl_xip_defconfig | 5 +++--
>
The following commits adds the configuration of firewalls required to
protect ATF and OP-TEE memory region from non-secure reads and
writes using master and slave firewalls present in our K3 SOCs.
Signed-off-by: Manorit Chawdhry
---
arch/arm/dts/k3-j7200-binman.dtsi | 137
The following commits adds the configuration of firewalls required to
protect ATF and OP-TEE memory region from non-secure reads and
writes using master and slave firewalls present in our K3 SOCs.
Signed-off-by: Manorit Chawdhry
---
arch/arm/dts/k3-j721s2-binman.dtsi | 206
The following commits adds the configuration of firewalls required to
protect ATF and OP-TEE memory region from non-secure reads and
writes using master and slave firewalls present in our K3 SOCs.
Signed-off-by: Manorit Chawdhry
---
arch/arm/dts/k3-am625-sk-binman.dtsi | 49
The following commits adds the configuration of firewalls required to
protect ATF and OP-TEE memory region from non-secure reads and
writes using master and slave firewalls present in our K3 SOCs.
Signed-off-by: Manorit Chawdhry
---
arch/arm/dts/k3-j721e-binman.dtsi | 183
For readability during configuring firewalls, adding k3-security.h file
and including it in k3-binman.dtsi to be accessible across K3 SoCs
Signed-off-by: Manorit Chawdhry
---
arch/arm/dts/k3-binman.dtsi | 2 ++
arch/arm/dts/k3-security.h | 58 +
2
Add test for TI firewalling node in ti-secure.
Signed-off-by: Manorit Chawdhry
---
tools/binman/ftest.py| 12
tools/binman/test/311_ti_secure_firewall.dts | 28
2 files changed, 40 insertions(+)
diff --git
We can now firewall entities while loading them through our secure
entity TIFS, the required information should be present in the
certificate that is being parsed by TIFS.
The following commit adds the support to enable the certificates to be
generated if the firewall configurations are present
HexOctet format is used by openssl for FORMAT:HEX,OCT property in x509
certificates. Add a helper function to extract the integer numbers in
HEX,OCT format to pass to openssl directly.
Signed-off-by: Manorit Chawdhry
---
tools/dtoc/fdt_util.py | 20
1 file changed, 20
K3 devices have firewalls that are used to prevent illegal accesses to
memory regions that are deemed secure. The series prevents the illegal
accesses to ATF and OP-TEE regions that are present in different K3
devices.
AM62AX and AM64X are currently in hold due to some firewall
configurations
Hi Heinrich,
On Sat, Sep 23, 2023 at 01:35:26AM +0200, Heinrich Schuchardt wrote:
> Most boards don't enable the pre-console buffer. So we will not see any
> early messages. OpenSBI 1.3 provides us with the debug console extension
> that can fill this gap.
>
> For S-Mode U-Boot enable
On Mon, Sep 25, 2023 at 1:28 PM Vignesh Raghavendra wrote:
>
> Hi,
>
> On 21/09/23 21:52, Masahiro Yamada wrote:
> > On Fri, Sep 22, 2023 at 12:03 AM Masahiro Yamada
> > wrote:
> >>
> >> Hi.
> >>
> >> I am seeing a boot failure on AM64-SK.
> >>
> >>
> >> I got the following error in SPL of the
On Thu, Sep 21, 2023 at 12:39:29PM +0200, Heinrich Schuchardt wrote:
> A 16 bit aligned instruction should generated an exception if the C
> extension is not available.
>
> Provide an 'extension ialign16' command for testing exception handling.
>
> For testing build qemu-riscv64_defconfig with
On Thu, Sep 21, 2023 at 10:42:18AM +0200, Heinrich Schuchardt wrote:
> Eliminating the C extension on application processors is under
> discussion.
>
> Support emitting a compressed instruction. This will lead to an
> illegal instruction exception if the C extension is not implemented.
>
> For
Hello,
> > > > > These are firmware bindings, as indicated, but I
> > > > > took them out of the /firmware node since that is for a different
> > > > > purpose. Rob suggested that partitions was a good place. We have fwupd
> > > > > using DT to hold the firmware-update information, so I expect it
On 9/26/2023 3:16 PM, Heinrich Schuchardt wrote:
> Remove dram_init_banksize() on the architecture level.
>
> Limiting used RAM to under 4 GiB is only necessary for CPUs which have a
> DMA issue. SoC specific code already exists for FU540, FU740, JH7110.
>
> Not all RISC-V boards will have
Remove dram_init_banksize() on the architecture level.
Limiting used RAM to under 4 GiB is only necessary for CPUs which have a
DMA issue. SoC specific code already exists for FU540, FU740, JH7110.
Not all RISC-V boards will have memory below 4 GiB.
A weak implementation of dram_init_banksize()
On Sat, Sep 23, 2023 at 01:35:26AM +0200, Heinrich Schuchardt wrote:
> Most boards don't enable the pre-console buffer. So we will not see any
> early messages. OpenSBI 1.3 provides us with the debug console extension
> that can fill this gap.
>
> For S-Mode U-Boot enable CONFIG_DEBUG_UART by
On 9/26/23 07:07, Anup Patel wrote:
On Thu, Sep 14, 2023 at 12:49 PM Heinrich Schuchardt wrote:
On 9/14/23 08:48, Wu, Fei wrote:
On 9/14/2023 2:05 PM, Heinrich Schuchardt wrote:
Am 14. September 2023 07:30:55 MESZ schrieb Fei Wu :
In order to enable PCIe passthrough on qemu riscv, the
This ut has tests for the SCMI power domain protocol as well as DM
interfaces for power domain devices.
Signed-off-by: AKASHI Takahiro
---
test/dm/scmi.c | 107 -
1 file changed, 106 insertions(+), 1 deletion(-)
diff --git a/test/dm/scmi.c
SCMI power domain management protocol is supported on sandbox
for test purpose. Add fake agent interfaces and associated
power domain devices.
Signed-off-by: AKASHI Takahiro
---
arch/sandbox/dts/test.dts| 6 +
arch/sandbox/include/asm/scmi_test.h | 20 ++
Add power domain driver based on SCMI power domain management protocol.
Signed-off-by: AKASHI Takahiro
---
drivers/firmware/scmi/scmi_agent-uclass.c | 11 ++
drivers/power/domain/Kconfig | 7 +
drivers/power/domain/Makefile | 1 +
In this patch, added are helper functions to directly manipulate
SCMI power domain management protocol. DM compliant power domain
driver will be implemented on top of those interfaces in a succeeding
patch.
Signed-off-by: AKASHI Takahiro
---
drivers/firmware/scmi/Makefile | 1 +
This patch series allows users to access SCMI power domain protocol
provided by SCMI server (platform). See SCMI specification document
v3.2 beta 2[1] for more details about SCMI power domain protocol.
The implementation consists of two layers:
- basic helper functions for SCMI power domain
In this test, "scmi" command is tested against different sub-commands.
Please note that scmi command is for debug purpose and is not intended
in production system.
Signed-off-by: AKASHI Takahiro
Reviewed-by: Simon Glass
Reviewed-by: Etienne Carriere
---
v4
* move 'base'-related changes to the
This is a help text for scmi command.
Signed-off-by: AKASHI Takahiro
Reviewed-by: Simon Glass
Reviewed-by: Etienne Carriere
---
v4
* s/tranport/transport/
v2
* add more descriptions about SCMI
---
doc/usage/cmd/scmi.rst | 126 +
1 file changed, 126
This command, "scmi", may provide a command line interface to various SCMI
protocols. It supports at least initially SCMI base protocol and is
intended mainly for debug purpose.
Signed-off-by: AKASHI Takahiro
Reviewed-by: Simon Glass
Reviewed-by: Etienne Carriere
---
v3
* describe that
Added is a new unit test for SCMI base protocol, which will exercise all
the commands provided by the protocol, except SCMI_BASE_NOTIFY_ERRORS.
$ ut dm scmi_base
It is assumed that test.dtb is used as sandbox's device tree.
Signed-off-by: AKASHI Takahiro
Reviewed-by: Etienne Carriere
---
v4
*
SCMI base protocol is mandatory and doesn't need to be listed in a device
tree.
Signed-off-by: AKASHI Takahiro
Reviewed-by: Simon Glass
Reviewed-by: Etienne Carriere
---
arch/sandbox/dts/test.dts | 4
1 file changed, 4 deletions(-)
diff --git a/arch/sandbox/dts/test.dts
Now that we have Base protocol support, we will be able to check if a given
protocol is really supported by the SCMI server (firmware).
Signed-off-by: AKASHI Takahiro
Reviewed-by: Etienne Carriere
---
v3
* new; import this patch from my followup patch set
---
SCMI base protocol is mandatory, and once SCMI node is found in a device
tree, the protocol handle (udevice) is unconditionally installed to
the agent. Then basic information will be retrieved from SCMI server via
the protocol and saved into the agent instance's local storage.
Signed-off-by:
Adding SCMI base protocol makes it inconvenient to hold the agent instance
(udevice) locally since the agent device will be re-created per each test.
Just remove it and simplify the test flows.
The test scenario is not changed at all.
Signed-off-by: AKASHI Takahiro
Reviewed-by: Simon Glass
This is a simple implementation of SCMI base protocol for sandbox.
The main use is in SCMI unit test.
Signed-off-by: AKASHI Takahiro
Reviewed-by: Simon Glass
Reviewed-by: Etienne Carriere
---
v4
* move this patch forward in this series before installing base
protocol to avoid collapsing
This framework allows SCMI protocols to be installed and bound to the agent
so that the agent can manage and utilize them later.
Signed-off-by: AKASHI Takahiro
Reviewed-by: Simon Glass
Reviewed-by: Etienne Carriere
---
V4
* remove 'agent' variable as it should be added in the following commit
Move the location of scmi_bind_protocols() backward for changes
in later patches.
There is no change in functionality.
Signed-off-by: AKASHI Takahiro
Reviewed-by: Simon Glass
Reviewed-by: Etienne Carriere
---
v4
* remove scmi_bind_protocols() from the original place. See patch#1
*
SCMI base protocol is mandatory according to the SCMI specification.
With this patch, SCMI base protocol can be accessed via SCMI transport
layers. All the commands, except SCMI_BASE_NOTIFY_ERRORS, are supported.
This is because U-Boot doesn't support interrupts and the current transport
layers
Any SCMI protocol may have its own channel.
Test this feature on sandbox as the necessary framework was added
in a prior commit.
Signed-off-by: AKASHI Takahiro
---
v5
* new commit
---
arch/sandbox/dts/test.dts | 1 +
test/dm/scmi.c| 20 ++--
2 files changed, 19
In sandbox scmi agent, channels are not used at all. But in this patch,
dummy channels are supported in order to test protocol-specific channels.
Signed-off-by: AKASHI Takahiro
---
v5
* new commit
---
arch/sandbox/include/asm/scmi_test.h | 13
SCMI specification allows any protocol to have its own channel for
the transport. While the current SCMI driver may assign its channel
from a device tree, the core function, devm_scmi_process_msg(), doesn't
use a protocol's channel, but always use an agent's channel.
With this commit,
The commit 85dc58289238 ("firmware: scmi: prepare uclass to pass channel
reference") added an explicit parameter, channel, but it seems to make
the code complex.
Hiding this parameter will allow for adding a generic (protocol-agnostic)
helper function, i.e. for PROTOCOL_VERSION, in a later patch.
This patch series allows users to access SCMI base protocol provided by
SCMI server (platform). It will also be utilized in separate patches
in the future to add sanity/validity checks for other protocols.
See SCMI specification document v3.2 beta[1] for more details about SCMI
base protocol.
Le 24/09/2023 à 21:24, Simon Glass a écrit :
> It doesn't make sense to have some boards do this differently. Drop the
> condition in the hope that the maintainers can figure out any run-time
> problems.
This was added by commit ea8256f072 ("SPL: Port SPL framework to
powerpc"), and the commit
On 25/09/2023 17.14, Jonas Karlman wrote:
>> fit,align
>> -Indicates what alignment to use for the FIT and its external data,
>> -and provides the alignment to use. This is passed to mkimage via
>> -the -B flag.
>> +Indicates what alignment to use for the FIT
On 22/09/23 12:30, Alexander Dahl wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
>
> Hello Durai,
>
> Am Thu, Sep 21, 2023 at 10:36:27PM +0530 schrieb Durai Manickam KR:
>> This patch series adds boot from NAND support, configs update and
>>
Hi Keerthy
On 9/25/2023 7:12 PM, Nishanth Menon wrote:
On 18:56-20230925, Keerthy wrote:
Hi Tom,
https://lore.kernel.org/linux-arm-kernel/5187c590-ee9a-4c46-b326-655f4c371...@linaro.org/T/#me178708007a6b3b9695ae0ff84475fa4f49f283c
I have posted the ESM patches to the linux kernel device tree
201 - 255 of 255 matches
Mail list logo
