> Same question as for v1, are we sure that the partition block size is
> the same as the MMC erase block size? Is this guaranteed by all
> standards (all MMC standards, and all partition table standards)?
> Otherwise I assume we should do some maths here to figure out the MMC
> start block AND blo
The mmc erase command currently requires blk# and cnt parameters
which can be obtained using the part start and part size commands
if the entire partition needs to be erased.
Simplify the use of the mmc erase command by allowing the partition
name to be specified directly.
Signed-off-by: Tomas
The mmc erase command currently requires blk# and cnt parameters
which can be obtained using the part start and part size commands
if the entire partition needs to be erased.
Simplify the use of the mmc erase command by allowing the partition
name to be specified directly.
---
cmd/mmc.c
The mmc erase command currently requires blk# and cnt parameters
which can be obtained using the part command if the entire partition
needs to be deleted.
Simplify the use of the mmc erase command by allowing the partition
name to be specified directly.
Signed-off-by: Tomas Paukrt
---
cmd
> Changelog is missing, what changed since V3 of this patch ?
There was a typo in V3 that caused compilation failure without CONFIG_DM_GPIO.
/4afc3f90943c6b117f79b66d2cd04e64f437b0c2
Signed-off-by: Tomas Paukrt
---
drivers/gpio/mxc_gpio.c | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/drivers/gpio/mxc_gpio.c b/drivers/gpio/mxc_gpio.c
index cac6b32..28176e1 100644
--- a/drivers/gpio/mxc_gpio.c
+++ b/drivers/gpio/mxc_gpio.c
@@ -133,7
> You may give a look to this
>
> https://lore.kernel.org/u-boot/57015c5f.3080...@denx.de/
>
> Regards,
> Peng.
The Linux driver uses the DR register for about 9 years and
the NXP U-Boot driver uses the DR register for about 7 years,
so only the mainline U-Boot driver still uses the PSR register.
driver already uses
the DR register for all GPIO pins in output mode:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=442b2494b17d1a4f0a14721580271eb23ebffd42
Signed-off-by: Tomas Paukrt
---
drivers/gpio/mxc_gpio.c | 10 --
1 file changed, 8 insertions(+), 2
for all GPIO pins in output mode:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=442b2494b17d1a4f0a14721580271eb23ebffd42
Signed-off-by: Tomas Paukrt
---
drivers/gpio/mxc_gpio.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpio
> For more information, please read this thread posted on
> linux-arm-kernel ten years ago:
>
> https://patchwork.kernel.org/project/linux-arm-kernel/patch/CAJ+vNU3w9Oi+dErmy9x8g6ps=eLHLNLO-w7=gn_8jty4kab...@mail.gmail.com/
>
> I hope this helps to clarify.
There is a good point that using the PSR
>> The PSR register works correctly for GPIO pins in input mode,
>> but always returns 0 for GPIO pins in output mode.
>> The DR register works correctly in both modes.
>
> The current code is correct as is.
> You should set the SION bit to read the value of the output pin.
Hi Fabio,
you are corr
Fix the dependency to avoid a warning if RSA_VERIFY_WITH_PKEY is enabled.
Fixes: b7463f198da6 ("Make ASYMMETRIC_KEY_TYPE depend on FIT_SIGNATURE")
Signed-off-by: Tomas Paukrt
---
lib/crypto/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/crypto/Kco
The PSR register works correctly for GPIO pins in input mode,
but always returns 0 for GPIO pins in output mode.
The DR register works correctly in both modes.
Signed-off-by: Tomas Paukrt
---
drivers/gpio/mxc_gpio.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers
13 matches
Mail list logo