* [PATCH 1/4] sched/topology: SD_ASYM_CPUCAPACITY flag detection
From: Morten Rasmussen @ 2018-07-24 8:37 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <b75f665f-7d60-5d83-eaf6-88c534afe254@arm.com>
On Mon, Jul 23, 2018 at 05:07:50PM +0100, Qais Yousef wrote:
> On 23/07/18 16:27, Morten Rasmussen wrote:
> >It does increase the cost of things like hotplug slightly and
> >repartitioning of root_domains a slightly but I don't see how we can
> >avoid it if we want generic code to set this flag. If the costs are not
> >acceptable I think the only option is to make the detection architecture
> >specific.
>
> I think hotplug is already expensive and this overhead would be small in
> comparison. But this could be called when frequency changes if I understood
> correctly - this is the one I wasn't sure how 'hot' it could be. I wouldn't
> expect frequency changes at a very high rate because it's relatively
> expensive too..
A frequency change shouldn't lead to a flag change or a rebuild of the
sched_domain hierarhcy. The situations where the hierarchy should be
rebuild to update the flag is during boot as we only know the amount of
asymmetry once cpufreq has been initialized, when cpus are hotplugged
in/out, and when root_domains change due to cpuset reconfiguration. So
it should be a relatively rare event.
^ permalink raw reply
* [U-Boot] [RFC PATCH] gpio: zynq: Setup bank_name to dev->name
From: Michal Simek @ 2018-07-24 8:37 UTC (permalink / raw)
To: u-boot
In-Reply-To: <589cfccf-dc79-c84f-f147-36a2ac7b4aee@herbrechtsmeier.net>
On 23.7.2018 20:29, Stefan Herbrechtsmeier wrote:
> Hi Michal,
>
>
> Am 23.07.2018 um 11:08 schrieb Michal Simek:
>> On 20.7.2018 21:31, Stefan Herbrechtsmeier wrote:
>>> Am 12.07.2018 um 16:04 schrieb Michal Simek:
>>>> There should be proper bank name setup to distiguish between different
>>>> gpio drivers. Use dev->name for it.
>>>>
>>>> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
>>>> ---
>>>>
>>>> drivers/gpio/zynq_gpio.c | 2 ++
>>>> 1 file changed, 2 insertions(+)
>>>>
>>>> diff --git a/drivers/gpio/zynq_gpio.c b/drivers/gpio/zynq_gpio.c
>>>> index 26f69b1a713f..f793ee5754a8 100644
>>>> --- a/drivers/gpio/zynq_gpio.c
>>>> +++ b/drivers/gpio/zynq_gpio.c
>>>> @@ -337,6 +337,8 @@ static int zynq_gpio_probe(struct udevice *dev)
>>>> struct zynq_gpio_privdata *priv = dev_get_priv(dev);
>>>> struct gpio_dev_priv *uc_priv = dev_get_uclass_priv(dev);
>>>> + uc_priv->bank_name = dev->name;
>>>> +
>>>> if (priv->p_data)
>>>> uc_priv->gpio_count = priv->p_data->ngpio;
>>>>
>>> Does this not lead to ugly names because the gpio number is append to
>>> the bank_name? Have you check the "gpio status -a" output?
>> Yes I was checking it. Names are composed together but also just numbers
>> works as before.
>>
>> gpio at ff0a00000: input: 0 [ ]
>> gpio at ff0a00001: input: 0 [ ]
>> gpio at ff0a00002: input: 0 [ ]
>> gpio at ff0a00003: input: 0 [ ]
>> gpio at ff0a00004: input: 0 [ ]
>> gpio at ff0a00005: input: 0 [ ]
>> gpio at ff0a00006: input: 0 [ ]
>> gpio at ff0a00007: input: 0 [ ]
>> gpio at ff0a00008: input: 0 [ ]
>> gpio at ff0a00009: input: 0 [ ]
>
> Do you think that this are meaningful names? It isn't possible to
> separate the device and pin number as well as it mix hex and decimal
> numbers.
>
>> If you know better way how to setup a bank name please let me know but I
>> need to distinguish ps gpio from pl one and for pl we need to know the
>> address.
>
> I know the use case.
>
> A lot of drivers use the bank_name from the device tree, some drivers
> append an underscore to the bank name and others add the req_seq of the
> device to an alphabetic character.
>
>>> Other drivers use the gpio-bank-name from the device tree.
>> I can't see this property inside Linux kernel. If this has been reviewed
>> by dt guys please let me know.
>
> This property is only used by u-boot. I think it isn't needed by the
> Linux kernel.
I am happy to use consistent solution but what's that?
Mixing name with hex and int is not nice but adding "_" or something
else is just a pain in driver code. If this is done in core I am fine
with that but adding this code to all drivers don't look like generic
solution at all.
Using additional u-boot property is not good too.
I have mentioned in "gpio: xilinx: Convert driver to DM"
(sha1:10441ec9224d0d269dc512819a32c0785a6338d3)
that uc-priv->name is completely unused. Maybe this should be dev->name
and bank_name should be really used for banks.
Then in gpio status -a can be
Device gpio at a0001000:
Bank:
...
but not sure how gpio commands will work to address exact pin from
prompt. Because this is normally working
gpio toggle gpio at a00010001
Thanks,
Michal
^ permalink raw reply
* [PATCH v2] net/mlx5: fix representors detection
From: Nelio Laranjeiro @ 2018-07-24 8:36 UTC (permalink / raw)
To: dev, Shahaf Shuler, Yongseok Koh
In-Reply-To: <df12520264499e27e96684783fe3381034f08192.1531489967.git.nelio.laranjeiro@6wind.com>
On systems where the required Netlink commands are not supported but
Mellanox OFED is installed, representors information must be retrieved
through sysfs.
Fixes: 4c10141488fe ("net/mlx5: add port representor awareness")
Signed-off-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
---
Changes in v2:
On some distribution, the PF may not be able to open the sysfs file,
such issue should not be handled as an error.
---
drivers/net/mlx5/mlx5.c | 7 +++--
drivers/net/mlx5/mlx5.h | 2 ++
drivers/net/mlx5/mlx5_ethdev.c | 53 ++++++++++++++++++++++++++++++++++
3 files changed, 60 insertions(+), 2 deletions(-)
diff --git a/drivers/net/mlx5/mlx5.c b/drivers/net/mlx5/mlx5.c
index 78a69228e..a1c0ad70a 100644
--- a/drivers/net/mlx5/mlx5.c
+++ b/drivers/net/mlx5/mlx5.c
@@ -1330,7 +1330,8 @@ mlx5_pci_probe(struct rte_pci_driver *pci_drv __rte_unused,
* Netlink calls assuming kernel drivers are recent enough to
* support them.
*
- * In the event of identification failure through Netlink, either:
+ * In the event of identification failure through Netlink, try again
+ * through sysfs, then either:
*
* 1. No device matches (n == 0), complain and bail out.
* 2. A single IB device matches (n == 1) and is not a representor,
@@ -1349,7 +1350,9 @@ mlx5_pci_probe(struct rte_pci_driver *pci_drv __rte_unused,
if (nl_route < 0 ||
!list[i].ifindex ||
mlx5_nl_switch_info(nl_route, list[i].ifindex,
- &list[i].info)) {
+ &list[i].info) ||
+ ((!list[i].info.representor && !list[i].info.master) &&
+ mlx5_sysfs_switch_info(list[i].ifindex, &list[i].info))) {
list[i].ifindex = 0;
memset(&list[i].info, 0, sizeof(list[i].info));
continue;
diff --git a/drivers/net/mlx5/mlx5.h b/drivers/net/mlx5/mlx5.h
index db8a5fa01..a7f50b31f 100644
--- a/drivers/net/mlx5/mlx5.h
+++ b/drivers/net/mlx5/mlx5.h
@@ -273,6 +273,8 @@ eth_rx_burst_t mlx5_select_rx_function(struct rte_eth_dev *dev);
unsigned int mlx5_dev_to_port_id(const struct rte_device *dev,
uint16_t *port_list,
unsigned int port_list_n);
+int mlx5_sysfs_switch_info(unsigned int ifindex,
+ struct mlx5_switch_info *info);
/* mlx5_mac.c */
diff --git a/drivers/net/mlx5/mlx5_ethdev.c b/drivers/net/mlx5/mlx5_ethdev.c
index 9cf2dc5f1..4a24f8021 100644
--- a/drivers/net/mlx5/mlx5_ethdev.c
+++ b/drivers/net/mlx5/mlx5_ethdev.c
@@ -1321,3 +1321,56 @@ mlx5_dev_to_port_id(const struct rte_device *dev, uint16_t *port_list,
}
return n;
}
+
+/**
+ * Get switch information associated with network interface.
+ *
+ * @param ifindex
+ * Network interface index.
+ * @param[out] info
+ * Switch information object, populated in case of success.
+ *
+ * @return
+ * 0 on success, a negative errno value otherwise and rte_errno is set.
+ */
+int
+mlx5_sysfs_switch_info(unsigned int ifindex, struct mlx5_switch_info *info)
+{
+ char ifname[IF_NAMESIZE];
+ FILE *file;
+ struct mlx5_switch_info data = { .master = 0, };
+ bool port_name_set = false;
+ bool port_switch_id_set = false;
+ char c;
+
+ if (!if_indextoname(ifindex, ifname)) {
+ rte_errno = errno;
+ return -rte_errno;
+ }
+
+ MKSTR(phys_port_name, "/sys/class/net/%s/phys_port_name",
+ ifname);
+ MKSTR(phys_switch_id, "/sys/class/net/%s/phys_switch_id",
+ ifname);
+
+ file = fopen(phys_port_name, "rb");
+ if (file != NULL) {
+ port_name_set =
+ fscanf(file, "%d%c", &data.port_name, &c) == 2 &&
+ c == '\n';
+ fclose(file);
+ }
+ file = fopen(phys_switch_id, "rb");
+ if (file == NULL) {
+ rte_errno = errno;
+ return -rte_errno;
+ }
+ port_switch_id_set =
+ fscanf(file, "%" SCNx64 "%c", &data.switch_id, &c) == 2 &&
+ c == '\n';
+ fclose(file);
+ data.master = port_switch_id_set && !port_name_set;
+ data.representor = port_switch_id_set && port_name_set;
+ *info = data;
+ return 0;
+}
--
2.18.0
^ permalink raw reply related
* [PATCH 3/3] iommu/arm-smmu: Error out only if not enough context interrupts
From: Will Deacon @ 2018-07-24 8:36 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20180719175356.14753-4-vivek.gautam@codeaurora.org>
On Thu, Jul 19, 2018 at 11:23:56PM +0530, Vivek Gautam wrote:
> Currently we check if the number of context banks is not equal to
> num_context_interrupts. However, there are booloaders such as, one
> on sdm845 that reserves few context banks and thus kernel views
> less than the total available context banks.
> So, although the hardware definition in device tree would mention
> the correct number of context interrupts, this number can be
> greater than the number of context banks visible to smmu in kernel.
> We should therefore error out only when the number of context banks
> is greater than the available number of context interrupts.
>
> Signed-off-by: Vivek Gautam <vivek.gautam@codeaurora.org>
> Suggested-by: Tomasz Figa <tfiga@chromium.org>
> Cc: Robin Murphy <robin.murphy@arm.com>
> Cc: Will Deacon <will.deacon@arm.com>
> ---
> drivers/iommu/arm-smmu.c | 19 +++++++++++++------
> 1 file changed, 13 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/iommu/arm-smmu.c b/drivers/iommu/arm-smmu.c
> index 7c69736a30f8..4cb53bf4f423 100644
> --- a/drivers/iommu/arm-smmu.c
> +++ b/drivers/iommu/arm-smmu.c
> @@ -2229,12 +2229,19 @@ static int arm_smmu_device_probe(struct platform_device *pdev)
> if (err)
> return err;
>
> - if (smmu->version == ARM_SMMU_V2 &&
> - smmu->num_context_banks != smmu->num_context_irqs) {
> - dev_err(dev,
> - "found only %d context interrupt(s) but %d required\n",
> - smmu->num_context_irqs, smmu->num_context_banks);
> - return -ENODEV;
> + if (smmu->version == ARM_SMMU_V2) {
> + if (smmu->num_context_banks > smmu->num_context_irqs) {
> + dev_err(dev,
> + "found only %d context irq(s) but %d required\n",
> + smmu->num_context_irqs, smmu->num_context_banks);
> + return -ENODEV;
> + } else if (smmu->num_context_banks < smmu->num_context_irqs) {
> + /* loose extra context interrupts */
> + dev_notice(dev,
> + "found %d context irq(s) but only %d required\n",
> + smmu->num_context_irqs, smmu->num_context_banks);
> + smmu->num_context_irqs = smmu->num_context_banks;
> + }
I don't see the utility in the new message. Can you simplify with the patch
below on top? It's a bit weird that we only decide to ignore the extra irqs
after calling platform_get_irq() on them, but that seems to be harmless.
Will
--->8
diff --git a/drivers/iommu/arm-smmu.c b/drivers/iommu/arm-smmu.c
index aa46c1ed5bf9..5349e22b5c78 100644
--- a/drivers/iommu/arm-smmu.c
+++ b/drivers/iommu/arm-smmu.c
@@ -2109,13 +2109,10 @@ static int arm_smmu_device_probe(struct platform_device *pdev)
"found only %d context irq(s) but %d required\n",
smmu->num_context_irqs, smmu->num_context_banks);
return -ENODEV;
- } else if (smmu->num_context_banks < smmu->num_context_irqs) {
- /* loose extra context interrupts */
- dev_notice(dev,
- "found %d context irq(s) but only %d required\n",
- smmu->num_context_irqs, smmu->num_context_banks);
- smmu->num_context_irqs = smmu->num_context_banks;
}
+
+ /* Ignore superfluous interrupts */
+ smmu->num_context_irqs = smmu->num_context_banks;
}
for (i = 0; i < smmu->num_global_irqs; ++i) {
^ permalink raw reply related
* Re: [PATCH 3/3] iommu/arm-smmu: Error out only if not enough context interrupts
From: Will Deacon @ 2018-07-24 8:36 UTC (permalink / raw)
To: Vivek Gautam
Cc: joro, robh+dt, robin.murphy, andy.gross, mark.rutland, iommu,
devicetree, linux-kernel, tfiga, sricharan, linux-arm-msm,
david.brown, linux-soc, linux-arm-kernel
In-Reply-To: <20180719175356.14753-4-vivek.gautam@codeaurora.org>
On Thu, Jul 19, 2018 at 11:23:56PM +0530, Vivek Gautam wrote:
> Currently we check if the number of context banks is not equal to
> num_context_interrupts. However, there are booloaders such as, one
> on sdm845 that reserves few context banks and thus kernel views
> less than the total available context banks.
> So, although the hardware definition in device tree would mention
> the correct number of context interrupts, this number can be
> greater than the number of context banks visible to smmu in kernel.
> We should therefore error out only when the number of context banks
> is greater than the available number of context interrupts.
>
> Signed-off-by: Vivek Gautam <vivek.gautam@codeaurora.org>
> Suggested-by: Tomasz Figa <tfiga@chromium.org>
> Cc: Robin Murphy <robin.murphy@arm.com>
> Cc: Will Deacon <will.deacon@arm.com>
> ---
> drivers/iommu/arm-smmu.c | 19 +++++++++++++------
> 1 file changed, 13 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/iommu/arm-smmu.c b/drivers/iommu/arm-smmu.c
> index 7c69736a30f8..4cb53bf4f423 100644
> --- a/drivers/iommu/arm-smmu.c
> +++ b/drivers/iommu/arm-smmu.c
> @@ -2229,12 +2229,19 @@ static int arm_smmu_device_probe(struct platform_device *pdev)
> if (err)
> return err;
>
> - if (smmu->version == ARM_SMMU_V2 &&
> - smmu->num_context_banks != smmu->num_context_irqs) {
> - dev_err(dev,
> - "found only %d context interrupt(s) but %d required\n",
> - smmu->num_context_irqs, smmu->num_context_banks);
> - return -ENODEV;
> + if (smmu->version == ARM_SMMU_V2) {
> + if (smmu->num_context_banks > smmu->num_context_irqs) {
> + dev_err(dev,
> + "found only %d context irq(s) but %d required\n",
> + smmu->num_context_irqs, smmu->num_context_banks);
> + return -ENODEV;
> + } else if (smmu->num_context_banks < smmu->num_context_irqs) {
> + /* loose extra context interrupts */
> + dev_notice(dev,
> + "found %d context irq(s) but only %d required\n",
> + smmu->num_context_irqs, smmu->num_context_banks);
> + smmu->num_context_irqs = smmu->num_context_banks;
> + }
I don't see the utility in the new message. Can you simplify with the patch
below on top? It's a bit weird that we only decide to ignore the extra irqs
after calling platform_get_irq() on them, but that seems to be harmless.
Will
--->8
diff --git a/drivers/iommu/arm-smmu.c b/drivers/iommu/arm-smmu.c
index aa46c1ed5bf9..5349e22b5c78 100644
--- a/drivers/iommu/arm-smmu.c
+++ b/drivers/iommu/arm-smmu.c
@@ -2109,13 +2109,10 @@ static int arm_smmu_device_probe(struct platform_device *pdev)
"found only %d context irq(s) but %d required\n",
smmu->num_context_irqs, smmu->num_context_banks);
return -ENODEV;
- } else if (smmu->num_context_banks < smmu->num_context_irqs) {
- /* loose extra context interrupts */
- dev_notice(dev,
- "found %d context irq(s) but only %d required\n",
- smmu->num_context_irqs, smmu->num_context_banks);
- smmu->num_context_irqs = smmu->num_context_banks;
}
+
+ /* Ignore superfluous interrupts */
+ smmu->num_context_irqs = smmu->num_context_banks;
}
for (i = 0; i < smmu->num_global_irqs; ++i) {
^ permalink raw reply related
* [U-Boot] [PATCH v2 09/13] sunxi: add UART0 setup for H6
From: Maxime Ripard @ 2018-07-24 8:36 UTC (permalink / raw)
To: u-boot
In-Reply-To: <20180721082032.39980-10-icenowy@aosc.io>
On Sat, Jul 21, 2018 at 04:20:28PM +0800, Icenowy Zheng wrote:
> The UART0 on H6 is available at PH bank (and PF bank, but the PF one is
> muxed with SD card).
>
> Add pinmux configuration.
>
> Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
> Reviewed-by: Andre Przywara <andre.przywara@arm.com>
Acked-by: Maxime Ripard <maxime.ripard@bootlin.com>
Maxime
--
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180724/cd521a75/attachment.sig>
^ permalink raw reply
* [U-Boot] [PATCH v2 05/13] sunxi: add config for SPL at 0x20000 on H6
From: Icenowy Zheng @ 2018-07-24 8:36 UTC (permalink / raw)
To: u-boot
In-Reply-To: <20180724083452.5s7egt5zophyrmve@flea>
于 2018年7月24日 GMT+08:00 下午4:34:52, Maxime Ripard <maxime.ripard@bootlin.com> 写到:
>On Sat, Jul 21, 2018 at 04:20:24PM +0800, Icenowy Zheng wrote:
>> On the new Allwinner H6 SoC, the SRAM A2 address (SPL load address)
>is
>> at 0x20000, which is different with any old Allwinner SoCs.
>>
>> Add SPL position and size configuration for this.
>>
>> Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
>> Reviewed-by: Andre Przywara <andre.przywara@arm.com>
>> ---
>> Changes in v2:
>> - Added Andre's Reviewed-by tag.
>>
>> include/configs/sunxi-common.h | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/include/configs/sunxi-common.h
>b/include/configs/sunxi-common.h
>> index 1b5daa8928..4db770d69d 100644
>> --- a/include/configs/sunxi-common.h
>> +++ b/include/configs/sunxi-common.h
>> @@ -199,6 +199,11 @@
>> #else
>> #define LOW_LEVEL_SRAM_STACK 0x00018000
>> #endif /* !CONFIG_ARM64 */
>> +#elif CONFIG_SUNXI_SRAM_ADDRESS == 0x20000
>> +#define CONFIG_SPL_TEXT_BASE 0x20060 /* sram start+header */
>> +#define CONFIG_SPL_MAX_SIZE 0x7fa0 /* 32 KiB */
>> +/* end of SRAM A2 on H6 for now */
>> +#define LOW_LEVEL_SRAM_STACK 0x00118000
>
>Can't we move those options to Kconfig, and deal with those changes
>there instead?
It's possible, but not any cleaner.
It will still be a hugh set of default xxx if xxx.
>
>Maxime
^ permalink raw reply
* Re: [PATCH 2/2] cpufreq: Fix a circular lock dependency problem
From: Rafael J. Wysocki @ 2018-07-24 8:36 UTC (permalink / raw)
To: Waiman Long
Cc: Peter Zijlstra, Rafael J. Wysocki, Viresh Kumar, Thomas Gleixner,
Ingo Molnar, Linux Kernel Mailing List, Linux PM,
Paul E. McKenney, Greg Kroah-Hartman, Konrad Rzeszutek Wilk
In-Reply-To: <0306d1b7-85d2-5e50-2b7c-466f0e978afa@redhat.com>
On Mon, Jul 23, 2018 at 9:27 PM, Waiman Long <longman@redhat.com> wrote:
> On 07/23/2018 03:16 PM, Peter Zijlstra wrote:
>> On Mon, Jul 23, 2018 at 01:49:39PM -0400, Waiman Long wrote:
>>> drivers/cpufreq/cpufreq.c | 16 +++++++++++++++-
>>> 1 file changed, 15 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
>>> index b0dfd32..9cf02d7 100644
>>> --- a/drivers/cpufreq/cpufreq.c
>>> +++ b/drivers/cpufreq/cpufreq.c
>>> @@ -922,8 +922,22 @@ static ssize_t store(struct kobject *kobj, struct attribute *attr,
>>> struct cpufreq_policy *policy = to_policy(kobj);
>>> struct freq_attr *fattr = to_attr(attr);
>>> ssize_t ret = -EINVAL;
>>> + int retries = 3;
>>>
>>> - cpus_read_lock();
>>> + /*
>>> + * cpus_read_trylock() is used here to work around a circular lock
>>> + * dependency problem with respect to the cpufreq_register_driver().
>>> + * With a simple retry loop, the chance of not able to get the
>>> + * read lock is extremely small.
>>> + */
>>> + while (!cpus_read_trylock()) {
>>> + if (retries-- <= 0)
>>> + return -EBUSY;
>>> + /*
>>> + * Sleep for about 50ms and retry again.
>>> + */
>>> + msleep(50);
>>> + }
>> That's atrocious.
>>
>>
> I had thought about just returning an error if the trylock fails as CPU
> hotplug rarely happened. I can revert to that simple case if others have
> no objection.
Yes, you can return -EBUSY or -EAGAIN right away from here if the
cpus_read_trylock() is not successful. There is not much reason for
the sysfs operation to continue in that case.
^ permalink raw reply
* [U-Boot] [PATCH v2 08/13] sunxi: use sun6i-style watchdog for H6
From: Maxime Ripard @ 2018-07-24 8:36 UTC (permalink / raw)
To: u-boot
In-Reply-To: <20180721082032.39980-9-icenowy@aosc.io>
On Sat, Jul 21, 2018 at 04:20:27PM +0800, Icenowy Zheng wrote:
> The H6 SoC has a sun6i-style watchdog in its timer part.
>
> Enable the usage of it.
>
> Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
Acked-by: Maxime Ripard <maxime.ripard@bootlin.com>
Maxime
--
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180724/56b27ff1/attachment.sig>
^ permalink raw reply
* [U-Boot] [PATCH v2 07/13] sunxi: add clock code for H6
From: Maxime Ripard @ 2018-07-24 8:35 UTC (permalink / raw)
To: u-boot
In-Reply-To: <20180721082032.39980-8-icenowy@aosc.io>
On Sat, Jul 21, 2018 at 04:20:26PM +0800, Icenowy Zheng wrote:
> The new Allwinner H6 SoC has a brand new CCU layout.
>
> Add clock code for it.
>
> Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
Acked-by: Maxime Ripard <maxime.ripard@bootlin.com>
Maxime
--
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180724/62329bdb/attachment.sig>
^ permalink raw reply
* [U-Boot] [PATCH v2 06/13] sunxi: change GIC address on H6
From: Maxime Ripard @ 2018-07-24 8:35 UTC (permalink / raw)
To: u-boot
In-Reply-To: <20180721082032.39980-7-icenowy@aosc.io>
On Sat, Jul 21, 2018 at 04:20:25PM +0800, Icenowy Zheng wrote:
> As the Allwinner H6 chip has a new memory map, its GIC MMIO address is
> thus different.
>
> Change the address on H6.
>
> Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
> Reviewed-by: Andre Przywara <andre.przywara@arm.com>
Acked-by: Maxime Ripard <maxime.ripard@bootlin.com>
Maxime
--
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180724/c895bc03/attachment.sig>
^ permalink raw reply
* [U-Boot] [PATCH v2 05/13] sunxi: add config for SPL at 0x20000 on H6
From: Maxime Ripard @ 2018-07-24 8:34 UTC (permalink / raw)
To: u-boot
In-Reply-To: <20180721082032.39980-6-icenowy@aosc.io>
On Sat, Jul 21, 2018 at 04:20:24PM +0800, Icenowy Zheng wrote:
> On the new Allwinner H6 SoC, the SRAM A2 address (SPL load address) is
> at 0x20000, which is different with any old Allwinner SoCs.
>
> Add SPL position and size configuration for this.
>
> Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
> Reviewed-by: Andre Przywara <andre.przywara@arm.com>
> ---
> Changes in v2:
> - Added Andre's Reviewed-by tag.
>
> include/configs/sunxi-common.h | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/include/configs/sunxi-common.h b/include/configs/sunxi-common.h
> index 1b5daa8928..4db770d69d 100644
> --- a/include/configs/sunxi-common.h
> +++ b/include/configs/sunxi-common.h
> @@ -199,6 +199,11 @@
> #else
> #define LOW_LEVEL_SRAM_STACK 0x00018000
> #endif /* !CONFIG_ARM64 */
> +#elif CONFIG_SUNXI_SRAM_ADDRESS == 0x20000
> +#define CONFIG_SPL_TEXT_BASE 0x20060 /* sram start+header */
> +#define CONFIG_SPL_MAX_SIZE 0x7fa0 /* 32 KiB */
> +/* end of SRAM A2 on H6 for now */
> +#define LOW_LEVEL_SRAM_STACK 0x00118000
Can't we move those options to Kconfig, and deal with those changes
there instead?
Maxime
--
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180724/2c2dc414/attachment.sig>
^ permalink raw reply
* Re: [PATCH] coreutils: fix compile error since use wrong libnss_nis.so
From: Robert Yang @ 2018-07-24 8:32 UTC (permalink / raw)
To: Richard Purdie, changqing.li, openembedded-core
In-Reply-To: <d1627eab4bff8883c6238d32c7704d4c29741d70.camel@linuxfoundation.org>
Hi RP,
On 07/09/2018 04:46 PM, Richard Purdie wrote:
> On Mon, 2018-07-09 at 15:49 +0800, changqing.li@windriver.com wrote:
>> From: Changqing Li <changqing.li@windriver.com>
>>
>> id: relocation error: /lib/x86_64-linux-gnu/libnss_nis.so.2:
>> symbol _nsl_default_nss version GLIBC_PRIVATE not defined in
>> file libnsl.so.1 with link time reference
>>
>> Recent glibc change removed libnss-nis module from glibc and
>> a new recipe libnss-nis.bb was added. After this change,
>> we need to include native libnss_nis in coreutils. otherwise,
>> with "nis" in host /etc/nssswitch.conf, id will use host
>> libnss_nis.so, which will cause above error
>>
>> Signed-off-by: Changqing Li <changqing.li@windriver.com>
>> ---
>> meta/recipes-core/coreutils/coreutils_8.29.bb | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> I think this would be fixed by a new version of uninative-tarball after
> the recent change to include libnss-nis in it. We should probably have
> a new release of uninative rather than starting to add these DEPENDS
> everywhere...
When do you plan to rebuild uninative-tarball, please ? I can help if needed.
// Robert
>
> Cheers,
>
> Richard
>
^ permalink raw reply
* Re: [PATCH v2] bcache: set max writeback rate when I/O request is idle
From: Stefan Priebe - Profihost AG @ 2018-07-24 8:33 UTC (permalink / raw)
To: Coly Li, linux-bcache; +Cc: linux-block, stable, Michael Lyle
In-Reply-To: <3017b789-5bb5-1767-3eef-3bf5dffb7126@suse.de>
Am 24.07.2018 um 10:28 schrieb Coly Li:
> On 2018/7/24 3:16 PM, Stefan Priebe - Profihost AG wrote:
>> Am 24.07.2018 um 06:03 schrieb Coly Li:
>>> Commit b1092c9af9ed ("bcache: allow quick writeback when backing idle")
>>> allows the writeback rate to be faster if there is no I/O request on a
>>> bcache device. It works well if there is only one bcache device attached
>>> to the cache set. If there are many bcache devices attached to a cache
>>> set, it may introduce performance regression because multiple faster
>>> writeback threads of the idle bcache devices will compete the btree level
>>> locks with the bcache device who have I/O requests coming.
>>>
>>> This patch fixes the above issue by only permitting fast writebac when
>>> all bcache devices attached on the cache set are idle. And if one of the
>>> bcache devices has new I/O request coming, minimized all writeback
>>> throughput immediately and let PI controller __update_writeback_rate()
>>> to decide the upcoming writeback rate for each bcache device.
>>>
>>> Also when all bcache devices are idle, limited wrieback rate to a small
>>> number is wast of thoughput, especially when backing devices are slower
>>> non-rotation devices (e.g. SATA SSD). This patch sets a max writeback
>>> rate for each backing device if the whole cache set is idle. A faster
>>> writeback rate in idle time means new I/Os may have more available space
>>> for dirty data, and people may observe a better write performance then.
>>>
>>> Please note bcache may change its cache mode in run time, and this patch
>>> still works if the cache mode is switched from writeback mode and there
>>> is still dirty data on cache.
>>>
>>> Fixes: Commit b1092c9af9ed ("bcache: allow quick writeback when backing idle")
>>> Cc: stable@vger.kernel.org #4.16+
>>> Signed-off-by: Coly Li <colyli@suse.de>
>>> Tested-by: Kai Krakow <kai@kaishome.de>
>>> Cc: Michael Lyle <mlyle@lyle.org>
>>> Cc: Stefan Priebe <s.priebe@profihost.ag>
>>
>> Hi Coly,
>>
>> i'm still experiencing the same bug as yesterday while rebooting every
>> two times i get a deadlock in cache_set_free.
>>
>> Sadly it's so late ion the shutdown process that netconsole is already
>> unloaded or at least i get no messages from while it happens. The traces
>> look the same like yesterday.
>
> Hi Stefan,
>
> Do you use the v2 patch on latest SLE15 kernel source?
Yes - i use the kernel code from here:
https://github.com/openSUSE/kernel-source/commits/SLE15
> Let me try to
> reproduce it on my machine. I assume when you reboot, the cache is still
> dirty and not clean up, am I right ?
Yes with around 15GB of dirty data - ceph is running on top of it and
generated many random writes.
> And which file system do you mount
> on top of the bcache device ?
XFS
>
> Thanks.
>
> Coly Li
Greets,
Stefan
^ permalink raw reply
* [PATCH] seabios: modify SRC_URI
From: Hongzhi.Song @ 2018-07-24 8:32 UTC (permalink / raw)
To: meta-virtualization
do_fetch fails because URL is wrong.
Signed-off-by: Hongzhi.Song <hongzhi.song@windriver.com>
---
recipes-extended/seabios/seabios_1.9.1.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-extended/seabios/seabios_1.9.1.bb b/recipes-extended/seabios/seabios_1.9.1.bb
index 144b13c..9206046 100644
--- a/recipes-extended/seabios/seabios_1.9.1.bb
+++ b/recipes-extended/seabios/seabios_1.9.1.bb
@@ -4,7 +4,7 @@ LICENSE = "LGPLv3"
SECTION = "firmware"
SRC_URI = " \
- https://code.coreboot.org/p/seabios/downloads/get/${PN}-${PV}.tar.gz \
+ https://code.coreboot.org/p/seabios/downloads/${PN}-${PV}.tar.gz \
file://hostcc.patch \
"
--
2.11.0
^ permalink raw reply related
* [PATCH] staging/vc04_services: Use __user annotation for user-space pointers
From: Carlos Maiolino @ 2018-07-24 8:32 UTC (permalink / raw)
To: linux-arm-kernel
Fix several sparse warnings regarding different address space
assignments, like example below, by properly annotating pointers
expected to carry user space addresses.
warning: incorrect type in argument 1 (different address spaces)
Signed-off-by: Carlos Maiolino <cmaiolino28@gmail.com>
---
I'm not subscribed to the list, so, please, CC me on any reply.
Thanks a lot.
drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c | 4 ++--
drivers/staging/vc04_services/interface/vchiq_arm/vchiq_ioctl.h | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c b/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c
index bc05c69383b8..42f471471e57 100644
--- a/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c
+++ b/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c
@@ -1648,8 +1648,8 @@ vchiq_compat_ioctl_queue_message(struct file *file,
unsigned int cmd,
unsigned long arg)
{
- VCHIQ_QUEUE_MESSAGE_T *args;
- struct vchiq_element *elements;
+ VCHIQ_QUEUE_MESSAGE_T __user *args;
+ struct vchiq_element __user *elements;
struct vchiq_queue_message32 args32;
unsigned int count;
diff --git a/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_ioctl.h b/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_ioctl.h
index 9f859953f45c..1776fab41e40 100644
--- a/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_ioctl.h
+++ b/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_ioctl.h
@@ -50,7 +50,7 @@ typedef struct {
typedef struct {
unsigned int handle;
unsigned int count;
- const struct vchiq_element *elements;
+ const struct vchiq_element __user *elements;
} VCHIQ_QUEUE_MESSAGE_T;
typedef struct {
--
2.14.3
^ permalink raw reply related
* [LTP] [PATCH] add testcases/lib/tst_supported_fs to .gititnore
From: Xiao Yang @ 2018-07-24 8:32 UTC (permalink / raw)
To: ltp
In-Reply-To: <20180724082530.18646-1-mmoese@suse.de>
Hi Michael,
Good catch. It looks good to me.
Reviewed-by: Xiao Yang <yangx.jy@cn.fujitsu.com>
Thanks,
Xiao Yang
On 2018/07/24 16:25, Michael Moese wrote:
> The binary tst_supported_fs was missing in the .gitinore file
> in testcases/lib, so it should be added.
>
> Signed-off-by: Michael Moese<mmoese@suse.de>
> ---
> testcases/lib/.gitignore | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/testcases/lib/.gitignore b/testcases/lib/.gitignore
> index 997940006..a9034e401 100644
> --- a/testcases/lib/.gitignore
> +++ b/testcases/lib/.gitignore
> @@ -7,4 +7,5 @@
> /tst_net_iface_prefix
> /tst_net_ip_prefix
> /tst_net_vars
> -/tst_getconf
> \ No newline at end of file
> +/tst_getconf
> +/tst_supported_fs
^ permalink raw reply
* pull-request: mac80211-next 2018-07-24
From: Johannes Berg @ 2018-07-24 7:25 UTC (permalink / raw)
To: David Miller; +Cc: netdev, linux-wireless
Hi Dave,
Also have a few changes for -next, figured I should get this
out too.
Please pull and let me know if there's any problem.
Thanks,
johannes
The following changes since commit c47078d6a33fd78d882200cdaacbcfcd63318234:
tcp: remove redundant SOCK_DONE checks (2018-07-08 17:14:58 +0900)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git tags/mac80211-next-for-davem-2018-07-24
for you to fetch changes up to 133bf90dbb8b873286f8ec2e81ba26e863114b8c:
mac80211: restrict delayed tailroom needed decrement (2018-07-24 09:21:12 +0200)
----------------------------------------------------------------
Only a few things:
* HE (802.11ax) support in HWSIM
* bypass TXQ with NDP frames as they're special
* convert ahash -> shash in lib80211 TKIP
* avoid playing with tailroom counter defer unless
needed to avoid issues in some cases
----------------------------------------------------------------
Ilan Peer (1):
mac80211_hwsim: Add support for HE
Johannes Berg (1):
mac80211: don't put null-data frames on the normal TXQ
Kees Cook (1):
wireless/lib80211: Convert from ahash to shash
Manikanta Pubbisetty (1):
mac80211: restrict delayed tailroom needed decrement
drivers/net/wireless/mac80211_hwsim.c | 123 ++++++++++++++++++++++++++++++++++
net/mac80211/cfg.c | 2 +-
net/mac80211/key.c | 24 ++++---
net/mac80211/tx.c | 2 +-
net/wireless/lib80211_crypt_tkip.c | 55 ++++++++-------
5 files changed, 170 insertions(+), 36 deletions(-)
^ permalink raw reply
* [U-Boot] [PATCH v2 04/13] sunxi: change ATF position for H6
From: Maxime Ripard @ 2018-07-24 8:32 UTC (permalink / raw)
To: u-boot
In-Reply-To: <20180721082032.39980-5-icenowy@aosc.io>
On Sat, Jul 21, 2018 at 04:20:23PM +0800, Icenowy Zheng wrote:
> H6 has different SRAM A2 address, so the ATF load address is also
> different.
>
> Add judgment code to sunxi 64-bit FIT generation script. It will judge
> the SoC by the device tree's name.
>
> Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
Acked-by: Maxime Ripard <maxime.ripard@bootlin.com>
Maxime
--
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180724/94786c72/attachment.sig>
^ permalink raw reply
* Re: [PATCH 2/2] cpufreq: Fix a circular lock dependency problem
From: Rafael J. Wysocki @ 2018-07-24 8:31 UTC (permalink / raw)
To: Peter Zijlstra
Cc: Waiman Long, Rafael J. Wysocki, Viresh Kumar, Thomas Gleixner,
Ingo Molnar, Linux Kernel Mailing List, Linux PM,
Paul E. McKenney, Greg Kroah-Hartman, Konrad Rzeszutek Wilk
In-Reply-To: <20180723191627.GJ2494@hirez.programming.kicks-ass.net>
On Mon, Jul 23, 2018 at 9:16 PM, Peter Zijlstra <peterz@infradead.org> wrote:
> On Mon, Jul 23, 2018 at 01:49:39PM -0400, Waiman Long wrote:
>> drivers/cpufreq/cpufreq.c | 16 +++++++++++++++-
>> 1 file changed, 15 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
>> index b0dfd32..9cf02d7 100644
>> --- a/drivers/cpufreq/cpufreq.c
>> +++ b/drivers/cpufreq/cpufreq.c
>> @@ -922,8 +922,22 @@ static ssize_t store(struct kobject *kobj, struct attribute *attr,
>> struct cpufreq_policy *policy = to_policy(kobj);
>> struct freq_attr *fattr = to_attr(attr);
>> ssize_t ret = -EINVAL;
>> + int retries = 3;
>>
>> - cpus_read_lock();
>> + /*
>> + * cpus_read_trylock() is used here to work around a circular lock
>> + * dependency problem with respect to the cpufreq_register_driver().
>> + * With a simple retry loop, the chance of not able to get the
>> + * read lock is extremely small.
>> + */
>> + while (!cpus_read_trylock()) {
>> + if (retries-- <= 0)
>> + return -EBUSY;
>> + /*
>> + * Sleep for about 50ms and retry again.
>> + */
>> + msleep(50);
>> + }
>
> That's atrocious.
Agreed.
^ permalink raw reply
* [U-Boot] [PATCH v2 03/13] sunxi: change RMR64's RVBAR address for H6
From: Maxime Ripard @ 2018-07-24 8:31 UTC (permalink / raw)
To: u-boot
In-Reply-To: <20180721082032.39980-4-icenowy@aosc.io>
On Sat, Jul 21, 2018 at 04:20:22PM +0800, Icenowy Zheng wrote:
> Allwinner H6 has a different RVBAR address with A64/H5.
>
> Add conditional RVBAR configuration into the code which does RMR switch.
>
> Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
> Reviewed-by: Andre Przywara <andre.przywara@arm.com>
Acked-by: Maxime Ripard <maxime.ripard@bootlin.com>
Maxime
--
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180724/7b60c3a9/attachment.sig>
^ permalink raw reply
* [Buildroot] [PATCH] vim: install /bin/vi as a relative symlink
From: Thomas Petazzoni @ 2018-07-24 8:30 UTC (permalink / raw)
To: buildroot
In-Reply-To: <93989b29-232f-20a2-4ac4-835066e5229b@mind.be>
Hello,
On Tue, 24 Jul 2018 09:55:40 +0200, Arnout Vandecappelle wrote:
> The thing is, I don't believe that relying on BR2_ROOTFS_MERGED_USR is the
> right approach. I've had projects with a usr -> . symlink in a custom skeleton,
> for instance. We could of course declare such a skeleton invalid, but I don't
> think that it is checked currently. Also I can imagine that there could be other
> custom skeleton layouts that could create problems.
>
> We already use ln --relative in a few places, isn't that the easiest solution?
ln --relative is not supported on old distros, we even have a patch on
systemd to remove its use of ln --relative.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
^ permalink raw reply
* Re: Build Error
From: hardik vala @ 2018-07-24 8:29 UTC (permalink / raw)
To: Burton, Ross; +Cc: Poky Project
In-Reply-To: <CAJTo0LbM4WH0JK4V7mYgMyNjf_S9v=uZEoWG_LMx-2B9mrjASA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 858 bytes --]
one meta provided by poky and other meta is openembedded-core/meta directory
From: "Burton, Ross" <ross.burton@intel.com>
To: hardik vala <hardik.vala@aumraj.com>
Cc: Poky Project <poky@yoctoproject.org>
Sent: Tuesday, 24 July 2018 1:40 PM
Subject: Re: [poky] Build Error
On 24 July 2018 at 08:11, hardik vala <hardik.vala@aumraj.com> wrote:
> meta
> meta-poky
> meta-yocto-bsp = "sumo:96fbd39ba32362416c18d90bb7a81eb6a76912e0"
> meta = "master:ff0b682b807959521c85716296de7a1d26d7d18f"
> meta-oe
> meta-python
> meta-networking = "master:0aff7abedc1c7727c88029a123107f4faf5ba4f1"
> meta-java = "master:ecb637a8cf5eb0cbff67e9e568858f7bfed061fc"
Why do you have meta twice, one with sumo and once with master? What
branch do you want to be using?
Ross
[-- Attachment #2: Type: text/html, Size: 2764 bytes --]
^ permalink raw reply
* [meta-oe][meta-python][PATCH] python-pyiface: Upgrade to version 0.0.9
From: Alexandru Vasiu @ 2018-07-24 8:27 UTC (permalink / raw)
To: openembedded-devel
Signed-off-by: Alexandru Vasiu <alexandru.vasiu@ni.com>
---
meta-python/recipes-devtools/python/python-pyiface.inc | 4 ++--
meta-python/recipes-devtools/python/python-pyiface_0.0.9.bb | 2 ++
meta-python/recipes-devtools/python/python3-pyiface_0.0.9.bb | 2 ++
3 files changed, 6 insertions(+), 2 deletions(-)
create mode 100644 meta-python/recipes-devtools/python/python-pyiface_0.0.9.bb
create mode 100644 meta-python/recipes-devtools/python/python3-pyiface_0.0.9.bb
diff --git a/meta-python/recipes-devtools/python/python-pyiface.inc b/meta-python/recipes-devtools/python/python-pyiface.inc
index 895a0ae09..a1156f428 100644
--- a/meta-python/recipes-devtools/python/python-pyiface.inc
+++ b/meta-python/recipes-devtools/python/python-pyiface.inc
@@ -5,7 +5,7 @@ LICENSE = "GPLv3+"
LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=4fe869ee987a340198fb0d54c55c47f1"
-SRC_URI[md5sum] = "1bbc53c281925eae5f508b8b1a1f8259"
-SRC_URI[sha256sum] = "83a64f5672cda48776ca9ed228dbf2e2df7b074a7dcb52ed4f6987322051928d"
+SRC_URI[md5sum] = "bc94e3d0c1cf8f49ac86514a8e90ed5c"
+SRC_URI[sha256sum] = "a58367d456ac0b4b9d1d5c31d5dd24363ad6c5bcc73edf027ded63732f784cf4"
inherit pypi
diff --git a/meta-python/recipes-devtools/python/python-pyiface_0.0.9.bb b/meta-python/recipes-devtools/python/python-pyiface_0.0.9.bb
new file mode 100644
index 000000000..854cb30ee
--- /dev/null
+++ b/meta-python/recipes-devtools/python/python-pyiface_0.0.9.bb
@@ -0,0 +1,2 @@
+inherit setuptools
+require python-pyiface.inc
\ No newline at end of file
diff --git a/meta-python/recipes-devtools/python/python3-pyiface_0.0.9.bb b/meta-python/recipes-devtools/python/python3-pyiface_0.0.9.bb
new file mode 100644
index 000000000..721e7b1c9
--- /dev/null
+++ b/meta-python/recipes-devtools/python/python3-pyiface_0.0.9.bb
@@ -0,0 +1,2 @@
+inherit setuptools3
+require python-pyiface.inc
--
2.18.0
^ permalink raw reply related
* [U-Boot] [PATCH v2 22/26] mmc: Change mode when switching to a boot partition
From: Faiz Abbas @ 2018-07-24 8:28 UTC (permalink / raw)
To: u-boot
In-Reply-To: <1506004213-22620-23-git-send-email-jjhiblot@ti.com>
Hi,
On Thursday 21 September 2017 08:00 PM, Jean-Jacques Hiblot wrote:
> Boot partitions do not support HS200. Changing to a lower performance mode
> is required to access them.
I see that the spec says "HS200 and HS400 modes are not supported during
*boot operation*". Can you point out where it says boot partitions are
not accessible in HS200/HS400?
I reverted this patch and was able to access boot0 partition in HS400
mode in U-boot.
Thanks,
Faiz
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.