On Mon, 9 Jun 2025 16:25:49 -0700
"Koralahalli Channabasappa, Smita"
wrote:
> On 6/9/2025 4:02 AM, Jonathan Cameron wrote:
> > On Tue, 3 Jun 2025 22:19:44 +
> > Smita Koralahalli wrote:
> >
> >> In preparation for soft-reserved resource handli
Hi Smita,
> >> +/*
> >> + * normalize_resource
> >> + *
> >> + * The walk_iomem_res_desc() returns a copy of a resource, not a reference
> >> + * to the actual resource in the iomem_resource tree. As a result,
> >> + * __release_resource() which relies on pointer equality will fail.
> >
> > Pro
On Tue, 3 Jun 2025 22:19:49 +
Smita Koralahalli wrote:
> From: Nathan Fontenot
>
> The DAX HMEM driver currently consumes all SOFT RESERVED iomem resources
> during initialization. This interferes with the CXL driver’s ability to
> create regions and trim overlapping SOFT RESERVED ranges be
On Tue, 3 Jun 2025 22:19:47 +
Smita Koralahalli wrote:
> Reworked from a patch by Alison Schofield
>
> Previously, when CXL regions were created through autodiscovery and their
> resources overlapped with SOFT RESERVED ranges, the soft reserved resource
> remained in place after region tear
On Tue, 3 Jun 2025 22:19:44 +
Smita Koralahalli wrote:
> In preparation for soft-reserved resource handling, make the suspend
> infrastructure always available by removing the CONFIG_CXL_SUSPEND
> Kconfig option.
>
> This ensures cxl_mem_active_inc()/dec() and cxl_mem_active() are
> uncondit
On Sun, 13 Apr 2025 17:52:09 -0500
Ira Weiny wrote:
> Per the CXL 3.1 specification software must check the Command Effects
> Log (CEL) for dynamic capacity command support.
>
> Detect support for the DCD commands while reading the CEL, including:
>
> Get DC Config
> Get DC Extent L
On Mon, 14 Apr 2025 21:50:31 -0700
Dan Williams wrote:
> Jonathan Cameron wrote:
> [..]
> > To me we don't need to answer the question of whether we fully understand
> > requirements, or whether this support covers them, but rather to ask
> > if anyone has requirem
On Sun, 13 Apr 2025 17:52:11 -0500
Ira Weiny wrote:
> Additional DCD partition (AKA region) information is contained in the
> DSMAS CDAT tables, including performance, read only, and shareable
> attributes.
>
> Match DCD partitions with DSMAS tables and store the meta data.
>
> Signed-off-by: I
On Sun, 13 Apr 2025 17:52:08 -0500
Ira Weiny wrote:
> A git tree of this series can be found here:
>
> https://github.com/weiny2/linux-kernel/tree/dcd-v6-2025-04-13
>
> This is now based on 6.15-rc2.
Hi Ira,
Firstly thanks for the update and your hard work driving this forwards.
>
> D
after the driver has loaded will surface through the normal notification
> path while extents seen prior to the driver are read during driver load.
>
> Based on an original patch by Navneet Singh.
>
> Reviewed-by: Jonathan Cameron
> Reviewed-by: Fan Ni
> Signed-off-by: Ira
> of 0 are allowed. This defines existing DAX devices as having a 0 tag
> which makes the most logical sense as a default.
>
> Process DCD events and create region devices.
>
> Based on an original patch by Navneet Singh.
>
> Reviewed-by: Dave Jiang
> Reviewed-
ned-off-by: Ira Weiny
>
I'm not that familiar with the DAX parts but looks fine to me.
Reviewed-by: Jonathan Cameron
On Sun, 13 Apr 2025 17:52:14 -0500
Ira Weiny wrote:
> Endpoints can now support a single dynamic ram partition following the
> persistent memory partition.
>
> Expand the mode to allow a decoder to point to the first dynamic ram
> partition.
>
> Signed-off-by: Ira Weiny
On Sun, 13 Apr 2025 17:52:13 -0500
Ira Weiny wrote:
> To properly configure CXL regions user space will need to know the
> details of the dynamic ram partition.
>
> Expose the first dynamic ram partition through sysfs.
>
> Signed-off-by: Ira Weiny
>
LGTM
Reviewed-by: Jonathan Cameron
he preservation of the implied
> partition order.
>
> Signed-off-by: Ira Weiny
One trivial thing inline.
To me this patch stands on it's own irrespective of the rest of the
series. Maybe one to queue up early as a cleanup?
Reviewed-by: Jonathan Cameron
Jonathan
> ---
&
On Sun, 13 Apr 2025 17:52:10 -0500
Ira Weiny wrote:
> Devices which optionally support Dynamic Capacity (DC) are configured
> via mailbox commands. CXL 3.2 section 9.13.3 requires the host to issue
> the Get DC Configuration command in order to properly configure DCDs.
> Without the Get DC Confi
On Thu, 3 Apr 2025 13:33:12 -0500
Terry Bowman wrote:
> From: Nathan Fontenot
>
> Add a release_Sam_region_adjustable() interface to allow for
Who is Sam? (typo)
> removing SOFT RESERVE memory resources. This extracts out the code
> to remove a mem region into a common __release_mem_region_a
c-aligned but block-misaligned chunks.
>
> Suggested-by: David Hildenbrand
> Suggested-by: Dan Williams
> Signed-off-by: Gregory Price
One trivial comment inline otherwise seems reasonable to me.
Reviewed-by: Jonathan Cameron
> ---
> drivers/dax/kmem.c | 10 +
On Thu, 3 Apr 2025 13:33:15 -0500
Terry Bowman wrote:
> From: Nathan Fontenot
>
> The dax hmem device initialization will consume any iomem
> SOFT RESERVE resources prior to CXL region creation. To allow
> for the CXL driver to complete region creation and trim any
> SOFT RESERVE resources befo
On Thu, 3 Apr 2025 13:33:14 -0500
Terry Bowman wrote:
> From: Nathan Fontenot
mum?
>
> In order to handle registering hmem devices for SOFT RESERVE
> resources after the dax hmem device initialization occurs
> we need to save a reference to the dax hmem platform device
> that will be used in
On Thu, 3 Apr 2025 13:33:13 -0500
Terry Bowman wrote:
> From: Nathan Fontenot
>
> Update handling of SOFT RESERVE iomem resources that intersect with
> CXL region resources to remove intersections from the SOFT RESERVE
> resources. The current approach of leaving SOFT RESERVE resources as
> is
On Mon, 17 Mar 2025 18:24:21 -0500
"Rob Herring (Arm)" wrote:
> Drivers with "memory-region" properties currently have to do their own
> parsing of "memory-region" properties. The result is all the drivers
> have similar patterns of a call to parse "memory-region" and then get
> the region's addr
On Sun, 9 Feb 2025 16:47:44 +0200
Andy Shevchenko wrote:
> On Sat, Feb 08, 2025 at 04:13:24PM -0500, Aren Moynihan wrote:
> > Using dev_err_probe instead of dev_err and return makes the errors
>
> Use dev_err_probe()
> dev_err()
>
> > easier to understand by including the error name, and save
On Tue, 12 Nov 2024 18:11:37 -0500
Aren wrote:
> On Tue, Nov 12, 2024 at 11:15:54AM +0100, Uwe Kleine-König wrote:
> > Hello Andy, hello Aren,
> >
> > On Mon, Nov 11, 2024 at 11:44:51AM +0200, Andy Shevchenko wrote:
> > > On Sun, Nov 10, 2024 at 04:34:30PM -0500, Aren wrote:
> > > > On Sun,
On Sat, 2 Nov 2024 15:50:39 -0400
Aren Moynihan wrote:
> The vdd and leda supplies must be powered on for the chip to function
> and can be powered off during system suspend.
>
> This was originally based on a patch by Ondrej Jirman[1], but has been
> rewritten since.
>
> 1:
> https://codeber
Hi Aren,
> @@ -624,7 +640,7 @@ static int stk3310_probe(struct i2c_client *client)
> device_property_read_u32(&client->dev, "proximity-near-level",
>&data->ps_near_level);
>
> - mutex_init(&data->lock);
> + devm_mutex_init(&client->dev, &data->lock);
On Mon, 28 Oct 2024 12:37:14 -0400
Aren Moynihan wrote:
> On Mon, Oct 28, 2024 at 04:38:37PM +0200, Andy Shevchenko wrote:
> > On Mon, Oct 28, 2024 at 10:19:57AM -0400, Aren Moynihan wrote:
> > > The vdd and leda supplies must be powered on for the chip to function
> > > and can be powered off
On Mon, 28 Oct 2024 10:19:54 -0400
Aren Moynihan wrote:
> In the Pine64 PinePhone, the stk3310 chip is powered by a regulator that is
> disabled at system boot and can be shut off during suspend. To ensure that
> the chip properly initializes, both after boot and suspend, we need to
> manage this
gt; PCIe Port.
>
> Signed-off-by: Ilpo Järvinen
My bash is terrible, but as far as I can tell this looks reasonable.
So with that in mind take this with a pinch of salt.
Reviewed-by: Jonathan Cameron
On Thu, 25 Jul 2024 14:50:50 +0100
David Woodhouse wrote:
> On Thu, 2024-07-25 at 08:33 -0400, Michael S. Tsirkin wrote:
> > On Thu, Jul 25, 2024 at 01:31:19PM +0100, David Woodhouse wrote:
> > > On Thu, 2024-07-25 at 08:29 -0400, Michael S. Tsirkin wrote:
> > > > On Thu, Jul 25, 2024 at 01:2
lks are now part of the generic code, move these
> functions from x86 to mm/numa_memblks.c and select
> CONFIG_NUMA_KEEP_MEMINFO when CONFIG_NUMA_MEMBLKS=y for dax and cxl.
>
> Signed-off-by: Mike Rapoport (Microsoft)
Reviewed-by: Jonathan Cameron
Thanks. I'll poke around more next week. Have a good weekend.
Jonathan
On Tue, 16 Jul 2024 14:13:41 +0300
Mike Rapoport wrote:
> From: "Mike Rapoport (Microsoft)"
>
> Move code dealing with numa_memblks from arch/x86 to mm/ and add Kconfig
> options to let x86 select it in its Kconfig.
>
> This code will be later reused by arch_numa.
>
> No functional changes.
>
On Tue, 16 Jul 2024 14:13:45 +0300
Mike Rapoport wrote:
> From: "Mike Rapoport (Microsoft)"
>
> Until now arch_numa was directly translating firmware NUMA information
> to memblock.
>
> Using numa_memblks as an intermediate step has a few advantages:
> * alignment with more battle tested x86 i
On Tue, 16 Jul 2024 14:13:44 +0300
Mike Rapoport wrote:
> From: "Mike Rapoport (Microsoft)"
>
> Introduce numa_memblks_init() and move some code around to avoid several
> global variables in numa_memblks.
Hi Mike,
Adding the effectively always on memblock_force_top_down
deserves a comment on
On Tue, 16 Jul 2024 14:13:42 +0300
Mike Rapoport wrote:
> From: "Mike Rapoport (Microsoft)"
>
> Move code dealing with numa_distance array from arch/x86 to
> mm/numa_memblks.c
It's not really numa memblock related. Is this the best place
to put it?
>
> This code will be later reused by arch_
numa emulation code with these architectures.
>
> Signed-off-by: Mike Rapoport (Microsoft)
Makes sense for both reasons. FWIW given how simple it is.
Maybe worth bringing a few more functions inline with this?
Probably something for another day given we don't care about the
inconsistency for this series.
Reviewed-by: Jonathan Cameron
ort (Microsoft)
Reviewed-by: Jonathan Cameron
t (Microsoft)
Not the most intuitive of function names but I can't immediately
think of a better one.
Reviewed-by: Jonathan Cameron
allocation.
>
> Replace memblock_phys_alloc_range() with memblock_alloc().
>
> Signed-off-by: Mike Rapoport (Microsoft)
Indeed seems to be after mapping physical memory, so this looks fine.
Reviewed-by: Jonathan Cameron
t; Signed-off-by: Mike Rapoport (Microsoft)
Reviewed-by: Jonathan Cameron
On Tue, 16 Jul 2024 14:13:35 +0300
Mike Rapoport wrote:
> From: "Mike Rapoport (Microsoft)"
>
> Allocation of numa_distance uses memblock_phys_alloc_range() to limit
> allocation to be below the last mapped page.
>
> But NUMA initializaition runs after the direct map is populated and
initiali
given
that file already has mix and match of those and normal prints in
single functions I assume this change is fine and we'll just
see the prints a bit later.
Reviewed-by: Jonathan Cameron
On Fri, 19 Jul 2024 17:07:35 +0200
David Hildenbrand wrote:
> >>> - * Allocate node data. Try node-local memory and then any node.
> >>> - * Never allocate in DMA zone.
> >>> - */
> >>> - nd_pa = memblock_phys_alloc_try_nid(nd_size, SMP_CACHE_BYTES, nid);
> >>> - if (!nd_pa) {
> >>> -
igned-off-by: Mike Rapoport (Microsoft)
Reviewed-by: Jonathan Cameron
t; Signed-off-by: Mike Rapoport (Microsoft)
FWIW rename looks fine
Reviewed-by: Jonathan Cameron
On Wed, 17 Jul 2024 16:32:59 +0200
David Hildenbrand wrote:
> On 16.07.24 13:13, Mike Rapoport wrote:
> > From: "Mike Rapoport (Microsoft)"
> >
> > sgi-ip27 is the only system that defines NODE_DATA() differently than
> > the rest of NUMA machines.
> >
> > Add node_data array of struct pglist
are in arch/*/mm not
arch/*/kernel so this makes it more consistent with that.
Reviewed-by: Jonathan Cameron
On Tue, 16 Jul 2024 14:13:29 +0300
Mike Rapoport wrote:
> From: "Mike Rapoport (Microsoft)"
>
> Hi,
>
> Following the discussion about handling of CXL fixed memory windows on
> arm64 [1] I decided to bite the bullet and move numa_memblks from x86 to
> the generic code so they will be available
On Tue, 23 Apr 2024 18:33:05 -0400
Aren Moynihan wrote:
> From: Ondrej Jirman
>
> VDD power input can be used to completely power off the chip during
> system suspend. Do so if available.
>
> Signed-off-by: Ondrej Jirman
> Signed-off-by: Aren Moynihan
Suggestions inline. Key thing is take
On Wed, 24 Apr 2024 18:20:41 +0300
Andy Shevchenko wrote:
> On Wed, Apr 24, 2024 at 3:59 PM Ondřej Jirman wrote:
> > On Wed, Apr 24, 2024 at 02:16:06AM GMT, Andy Shevchenko wrote:
> > > On Wed, Apr 24, 2024 at 1:41 AM Aren Moynihan
> > > wrote:
>
> ...
>
> > > > ret = stk3310_ini
On Wed, 24 Apr 2024 02:16:06 +0300
Andy Shevchenko wrote:
> On Wed, Apr 24, 2024 at 1:41 AM Aren Moynihan wrote:
> >
> > From: Ondrej Jirman
> >
> > VDD power input can be used to completely power off the chip during
> > system suspend. Do so if available.
>
> ...
>
> > ret = stk331
On Mon, 15 Apr 2024 18:05:54 +0300
Andy Shevchenko wrote:
> On Sun, Apr 14, 2024 at 8:57 PM Aren Moynihan wrote:
> >
> > If the chip isn't powered, this call is likely to return an error.
> > Without a log here the driver will silently fail to probe. Common errors
> > are ENXIO (when the chip is
On Sun, 14 Apr 2024 13:57:13 -0400
Aren Moynihan wrote:
> Signed-off-by: Aren Moynihan
> ---
> Documentation/devicetree/bindings/iio/light/stk33xx.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/iio/light/stk33xx.yaml
> b/Documentation/devicetre
On Sun, 14 Apr 2024 13:57:14 -0400
Aren Moynihan wrote:
> From: Ondrej Jirman
>
> VDD power input can be used to completely power off the chip during
> system suspend. Do so if available.
I'd make this non optional (relying on regulator framework providing
us a stub for old DT etc) and pay the
type is created for storing all memory types that are
> not initialized by device drivers and as a fallback.
>
> Signed-off-by: Ho-Ren (Jack) Chuang
> Signed-off-by: Hao Xiang
> Reviewed-by: "Huang, Ying"
Reviewed-by: Jonathan Cameron
On Tue, 9 Apr 2024 08:36:08 +0200
Krzysztof Kozlowski wrote:
> On 08/04/2024 18:34, Luca Weiss wrote:
> > Before all supported sensors except for MPU{9150,9250,9255} were not
> > allowed to use i2c-gate in the bindings which excluded quite a few
> > supported sensors where this functionality is s
On Tue, 9 Apr 2024 12:02:31 -0700
"Ho-Ren (Jack) Chuang" wrote:
> Hi Jonathan,
>
> On Tue, Apr 9, 2024 at 9:12 AM Jonathan Cameron
> wrote:
> >
> > On Fri, 5 Apr 2024 15:43:47 -0700
> > "Ho-Ren (Jack) Chuang" wrote:
> >
> >
On Fri, 5 Apr 2024 15:43:47 -0700
"Ho-Ren (Jack) Chuang" wrote:
> On Fri, Apr 5, 2024 at 7:03 AM Jonathan Cameron
> wrote:
> >
> > On Fri, 5 Apr 2024 00:07:06 +
> > "Ho-Ren (Jack) Chuang" wrote:
> >
> > > The current implemen
On Sat, 06 Apr 2024 17:31:04 +0200
Luca Weiss wrote:
> For example the BMP280 barometric pressure sensor on Qualcomm
> MSM8974-based Nexus 5 smartphone exposes such file in sysfs.
> Document it.
>
> Signed-off-by: Luca Weiss
Hi Luca,
Applied with a note added on fixing the line above to not r
On Fri, 5 Apr 2024 00:07:06 +
"Ho-Ren (Jack) Chuang" wrote:
> The current implementation treats emulated memory devices, such as
> CXL1.1 type3 memory, as normal DRAM when they are emulated as normal memory
> (E820_TYPE_RAM). However, these emulated devices have different
> characteristics t
gned-off-by: Ho-Ren (Jack) Chuang
> Reviewed-by: "Huang, Ying"
Reviewed-by: Jonathan Cameron
> > > @@ -858,7 +910,8 @@ static int __init memory_tier_init(void)
> > >* For now we can have 4 faster memory tiers with smaller adistance
> > >* than default DRAM tier.
> > >*/
> > > - default_dram_type = alloc_memory_type(MEMTIER_ADISTANCE_DRAM);
> > > + default_
A few minor comments inline.
> diff --git a/include/linux/memory-tiers.h b/include/linux/memory-tiers.h
> index a44c03c2ba3a..16769552a338 100644
> --- a/include/linux/memory-tiers.h
> +++ b/include/linux/memory-tiers.h
> @@ -140,12 +140,13 @@ static inline int mt_perf_to_adistance(struct
> acces
On Tue, 2 Apr 2024 00:17:37 +
"Ho-Ren (Jack) Chuang" wrote:
> Since different memory devices require finding, allocating, and putting
> memory types, these common steps are abstracted in this patch,
> enhancing the scalability and conciseness of the code.
>
> Signed-off-by: Ho-Ren (Jack) Ch
On Wed, 14 Feb 2024 17:33:18 -0500
Steven Rostedt wrote:
> On Wed, 14 Feb 2024 14:19:19 -0800
> Ira Weiny wrote:
>
> > > > Jonathan Cameron wrote:
> > > >
> > > > > So I'm thinking this is a won't fix - wait for the printk r
On Wed, 14 Feb 2024 10:23:10 -0500
Steven Rostedt wrote:
> On Wed, 14 Feb 2024 12:11:53 +
> Jonathan Cameron wrote:
>
> > So I'm thinking this is a won't fix - wait for the printk rework to land and
> > assume this will be resolved as well?
>
> That
On Tue, 06 Feb 2024 14:15:32 -0800
Ira Weiny wrote:
> Smatch caught that cxl_cper_post_event() is called with a spinlock held
> or preemption disabled.[1] The callback takes the device lock to
> perform address translation and therefore might sleep. The record data
> is released back to BIOS in
x/bus.c benefit from a cleanup using these, so change these
> where applicable.
>
> Cc: Joao Martins
> Cc: Dan Williams
> Signed-off-by: Vishal Verma
Hi Vishal,
A few really minor suggestions inline if you happen to be doing a v7.
Either way
Reviewed-by: Jonathan Cameron
On Tue, 12 Dec 2023 12:08:30 -0700
Vishal Verma wrote:
> Add the missing sysfs ABI documentation for the device DAX subsystem.
> Various ABI attributes under this have been present since v5.1, and more
> have been added over time. In preparation for adding a new attribute,
> add this file with th
On Tue, 12 Dec 2023 12:08:31 -0700
Vishal Verma wrote:
> Introduce a guard(device) macro to lock a 'struct device', and unlock it
> automatically when going out of scope using Scope Based Resource
> Management semantics. A lot of the sysfs attribute writes in
> drivers/dax/bus.c benefit from a cl
On Fri, 24 Nov 2023 10:21:21 +0100
Krzysztof Kozlowski wrote:
> Use only one and exactly one space around '=' in DTS example.
>
> Signed-off-by: Krzysztof Kozlowski
>
Acked-by: Jonathan Cameron #for-iio
> ---
>
> Merging idea: Rob's DT.
>
On Fri, 13 Oct 2023 10:09:53 +0200
Luca Weiss wrote:
> Add the defines for the ADC channels found on the PM7325. The list is
> taken from downstream msm-5.4 and adjusted for mainline.
>
> Signed-off-by: Luca Weiss
I assume this will go with the dts changes that use it.
Acked-
formance attributes separately.
>
> Signed-off-by: "Huang, Ying"
> Cc: Aneesh Kumar K.V
> Cc: Wei Xu
> Cc: Alistair Popple
> Cc: Dan Williams
> Cc: Dave Hansen
> Cc: Davidlohr Bueso
> Cc: Johannes Weiner
> Cc: Jonathan Cameron
> Cc: Michal Hocko
>
-by: Vishal Verma
Hi Vishal,
In general looks fine to me. Just a question for potential discussion if didn't
miss it in earlier versions.
FWIW
Reviewed-by: Jonathan Cameron
Also, any docs need updating? Doesn't seem like the DAX ABI docs are present in
Documentation/ABI so not sur
On Tue, 01 Aug 2023 23:55:37 -0600
Vishal Verma wrote:
> The MHP_MEMMAP_ON_MEMORY flag for hotplugged memory is restricted to
> 'memblock_size' chunks of memory being added. Adding a larger span of
> memory precludes memmap_on_memory semantics.
>
> For users of hotplug such as kmem, large amount
On Fri, 16 Jun 2023 09:46:59 +0200
David Hildenbrand wrote:
> On 16.06.23 00:00, Vishal Verma wrote:
> > For memory hotplug to consider MHP_MEMMAP_ON_MEMORY behavior, the
> > 'memmap_on_memory' module parameter was a hard requirement.
> >
> > In preparation for the dax/kmem driver to use memmap_
On Mon, 19 Apr 2021 20:45:08 +0100
Jonathan Cameron wrote:
> On Mon, 19 Apr 2021 16:34:35 +0300
> Tomas Melin wrote:
>
> > Hi,
> >
> > On 4/18/21 1:03 PM, Jonathan Cameron wrote:
> > > On Fri, 16 Apr 2021 15:21:14 +0300
> > > Tomas Melin wrot
On Mon, 19 Apr 2021 16:34:35 +0300
Tomas Melin wrote:
> Hi,
>
> On 4/18/21 1:03 PM, Jonathan Cameron wrote:
> > On Fri, 16 Apr 2021 15:21:14 +0300
> > Tomas Melin wrote:
> >
> >> Updated email-address for Alexandru.
> >>
> >>
> >&g
On Sun, 18 Apr 2021 16:59:02 +0300
Andy Shevchenko wrote:
> On Sun, Apr 18, 2021 at 4:49 PM Andy Shevchenko
> wrote:
> >
> > On Sun, Apr 18, 2021 at 2:07 PM Jonathan Cameron wrote:
> >
> > Thanks for review, my answers below.
> >
> > > On Wed, 14
On Fri, 16 Apr 2021 16:45:46 +0300
Tomas Melin wrote:
> Add initial support for Murata SCA3300 3-axis industrial
> accelerometer with digital SPI interface. This device also
> provides a temperature measurement.
>
> Device product page including datasheet can be found at:
> https://www.murata.co
On Sat, 17 Apr 2021 15:39:12 +0300
Andy Shevchenko wrote:
> On Fri, Apr 16, 2021 at 5:21 PM Tomas Melin wrote:
> >
> > Add initial support for Murata SCA3300 3-axis industrial
> > accelerometer with digital SPI interface. This device also
> > provides a temperature measurement.
> >
> > Device pr
On Thu, 15 Apr 2021 11:52:31 -0700
Srinivas Pandruvada wrote:
> In the function sensor_hub_set_feature(), return error when hid_set_field()
> fails.
>
> Signed-off-by: Srinivas Pandruvada
Series applied to the to greg branch of iio.git. Note these won't make the
coming merge window, so will tu
On Wed, 14 Apr 2021 22:54:53 +0300
Andy Shevchenko wrote:
> We can utilize separate drivers for accelerometer and magnetometer,
> so here is the glue driver to enable LSM9DS0 IMU support.
>
> The idea was suggested by Crestez Dan Leonard in [1]. The proposed change
> was sent as RFC due to race
On Wed, 14 Apr 2021 22:54:51 +0300
Andy Shevchenko wrote:
> In case we would initialize two IIO devices from one physical device,
> we shouldn't have a clash on regulators. That's why move
> st_sensors_power_enable() call from core to bus drivers.
Why is this a problem? The two instances would
On Thu, 15 Apr 2021 09:58:33 -0700
Srinivas Pandruvada wrote:
> On Wed, 2021-04-14 at 11:49 +0300, Alexandru Ardelean wrote:
> > During commit 067fda1c065ff ("iio: hid-sensors: move triggered buffer
> > setup into hid_sensor_setup_trigger"), the
> > iio_triggered_buffer_{setup,cleanup}() function
On Mon, 12 Apr 2021 16:18:35 +0300
Andy Shevchenko wrote:
> Enable ADC on Intel Galileo Gen 1 board.
>
> Signed-off-by: Andy Shevchenko
Applied to the togreg branch of iio.git and pushed out as testing for
the autobuilders to hopefully not notice we did anything ;)
Jonathan
> ---
> v2: fixed
On Fri, 16 Apr 2021 15:21:14 +0300
Tomas Melin wrote:
> Updated email-address for Alexandru.
>
>
> On 4/16/21 3:17 PM, Tomas Melin wrote:
> > On 4/15/21 11:41 AM, Tomas Melin wrote:
> >
> >>
> >> While working on updates I did notice something new which I cannot
> >>
> >> reproduce on older (
On Sun, 11 Apr 2021 21:08:29 +0300
Andy Shevchenko wrote:
> On Sun, Apr 11, 2021 at 9:07 PM Andy Shevchenko
> wrote:
> > On Sun, Apr 11, 2021 at 5:53 PM Jonathan Cameron wrote:
> > > On Wed, 7 Apr 2021 23:51:47 +0530
> > > Puranjay Mohan wrote:
>
>
On Mon, 12 Apr 2021 12:23:43 +0300
Andy Shevchenko wrote:
> On Mon, Apr 12, 2021 at 8:32 AM Dinghao Liu wrote:
> >
> > When lidar_write_control() fails, a pairing PM usage counter
> > decrement is needed to keep the counter balanced.
>
> You forgot to collect given tags.
>
> > Fixes: 4ac4e08
On Mon, 12 Apr 2021 13:47:58 +0200
Linus Walleij wrote:
> On Mon, Apr 12, 2021 at 12:16 PM Jonathan Cameron
> wrote:
>
> > An example would be the bmc150_magn driver which does exactly the
> > same call sequence as this one, but without the reference count increm
On Fri, 16 Apr 2021 18:49:01 +0100
Joe Sandom wrote:
> Driver implementation for AMS/TAOS tsl2591 ambient light sensor.
>
> This driver supports configuration via device tree and sysfs.
> Supported channels for raw infrared light intensity,
> raw combined light intensity and illuminance in lux.
omment. Refer
> Documentation/doc-guide/kernel-doc.rst
>
> Cc: Lars-Peter Clausen
> Cc: Michael Hennerich
> Cc: Jonathan Cameron
> Cc: Greg Kroah-Hartman
> Cc: linux-...@vger.kernel.org
> Cc: linux-stag...@lists.linux.dev
> Signed-off-by: Lee Jones
I was leaving the sta
On Mon, 12 Apr 2021 18:30:53 +0300
wrote:
> From: Ben Peled
>
> In PCIE ISR routine caused by RST_LINK_DOWN
> we schedule work to handle the link-down procedure.
> Link-down procedure will:
> 1. Remove PCIe bus
> 2. Reset the MAC
> 3. Reconfigure link back up
> 4. Rescan PCIe bus
>
> Signed-of
> Signed-off-by: Ben Widawsky
Checked all the numbers (not much else in this one ;)
Reviewed-by: Jonathan Cameron
You could give more info on why this particular list, but to my
mind it's all fairly obvious so perhaps not worth bothering.
> ---
> drivers/cxl/mem.c|
On Tue, 13 Apr 2021 07:32:47 -0700
Ben Widawsky wrote:
> Signed-off-by: Ben Widawsky
Sensible update.
Acked-by: Jonathan Cameron
> ---
> include/uapi/linux/cxl_mem.h | 7 +++
> 1 file changed, 7 insertions(+)
>
> diff --git a/include/uapi/linux/cxl_mem.h b/include/ua
On Tue, 13 Apr 2021 09:17:26 -0700
Ben Widawsky wrote:
> On 21-04-08 18:26:35, Jonathan Cameron wrote:
> > On Wed, 7 Apr 2021 15:26:22 -0700
> > Ben Widawsky wrote:
> >
> > > @cxlm.base only existed to support holding the base found in the
> > > registe
On Tue, 13 Apr 2021 17:42:37 -0700
Dan Williams wrote:
> On Tue, Apr 13, 2021 at 5:18 PM Dan Williams wrote:
> >
> > On Tue, Apr 6, 2021 at 10:47 AM Jonathan Cameron
> > wrote:
> > >
> > > On Thu, 1 Apr 2021 07:30:47 -0700
> > > Dan Williams w
On Mon, 12 Apr 2021 12:20:22 -0700
Shakeel Butt wrote:
> On Fri, Apr 9, 2021 at 4:26 PM Tim Chen wrote:
> >
> >
> > On 4/8/21 4:52 AM, Michal Hocko wrote:
> >
> > >> The top tier memory used is reported in
> > >>
> > >> memory.toptier_usage_in_bytes
> > >>
> > >> The amount of top tier memory
On Mon, 12 Apr 2021 10:50:56 +0300
Tomas Melin wrote:
> Add initial support for Murata SCA3300 3-axis industrial
> accelerometer with digital SPI interface. This device also
> provides a temperature measurement.
>
> Device product page including datasheet can be found at:
> https://www.murata.co
On Mon, 12 Apr 2021 10:50:55 +0300
Tomas Melin wrote:
> initial DT bindings for Murata SCA3300 Accelerometer.
>
> Signed-off-by: Tomas Melin
Hi Tomas.
> ---
> .../bindings/iio/accel/sca3300.yaml | 51 +++
> 1 file changed, 51 insertions(+)
> create mode 100644 Docume
1 - 100 of 2544 matches
Mail list logo
