mbox series

[00/37] nvmem: patches for 6.3

Message ID 20230127111605.25958-1-srinivas.kandagatla@linaro.org
Headers
Series nvmem: patches for 6.3 |

Message

Srinivas Kandagatla Jan. 27, 2023, 11:15 a.m. UTC 
  Hi Greg,

Here are some nvmem patches bit more than usual for 6.3 which includes

- Adding support for nvmem layouts, thanks to Michael and Miquel for
  driving this effort.
- Add support to stm32 STM32MP15x OPTEE based nvmem provider
- Updated to qfprom bindings to include various Qualcomm SoCs.
- adding sl28vpd provider layout
- move imx provider to use new layout apis
- add ONIE provider layout. 
- new helper eth_addr_add().
- few minor enhancements to core and providersdrivers.

Can you please queue them up for 6.3.

thanks for you help,
srini

MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

AngeloGioacchino Del Regno (1):
  dt-bindings: nvmem: Fix qcom,qfprom compatibles enum ordering

Arnd Bergmann (1):
  nvmem: stm32: fix OPTEE dependency

Colin Ian King (2):
  nvmem: layouts: Fix spelling mistake "platforn" -> "platform"
  dt-bindings: nvmem: Fix spelling mistake "platforn" -> "platform"

Johan Hovold (1):
  nvmem: qcom-spmi-sdam: register at device init time

Konrad Dybcio (2):
  dt-bindings: nvmem: Add compatible for SM8150
  dt-bindings: nvmem: Add compatible for SM8250

Marijn Suijten (1):
  dt-bindings: nvmem: Add compatible for MSM8976

Michael Walle (19):
  net: add helper eth_addr_add()
  of: base: add of_parse_phandle_with_optional_args()
  of: property: make #.*-cells optional for simple props
  of: property: add #nvmem-cell-cells property
  nvmem: core: add an index parameter to the cell
  nvmem: core: move struct nvmem_cell_info to nvmem-provider.h
  nvmem: core: drop the removal of the cells in nvmem_add_cells()
  nvmem: core: add nvmem_add_one_cell()
  nvmem: core: use nvmem_add_one_cell() in nvmem_add_cells_from_of()
  nvmem: core: introduce NVMEM layouts
  nvmem: core: add per-cell post processing
  nvmem: core: allow to modify a cell before adding it
  nvmem: imx-ocotp: replace global post processing with layouts
  nvmem: cell: drop global cell_post_process
  nvmem: core: provide own priv pointer in post process callback
  nvmem: layouts: add sl28vpd layout
  MAINTAINERS: add myself as sl28vpd nvmem layout driver
  nvmem: core: return -ENOENT if nvmem cell is not found
  of: property: fix #nvmem-cell-cells parsing

Miquel Raynal (2):
  nvmem: layouts: Add ONIE tlv layout driver
  MAINTAINERS: Add myself as ONIE tlv NVMEM layout maintainer

Patrick Delaunay (2):
  nvmem: stm32: add OP-TEE support for STM32MP13x
  nvmem: stm32: detect bsec pta presence for STM32MP15x

Rafał Miłecki (1):
  nvmem: core: fix nvmem_layout_get_match_data()

Randy Dunlap (1):
  nvmem: rave-sp-eeprm: fix kernel-doc bad line warning

Richard Acayan (1):
  dt-bindings: nvmem: qfprom: add sdm670 compatible

Robert Marko (1):
  dt-bindings: nvmem: qfprom: add IPQ8074 compatible

Russell King (Oracle) (1):
  nvmem: core: remove spurious white space

Samuel Holland (1):
  nvmem: sunxi_sid: Drop the workaround on A64

 .../nvmem/layouts/onie,tlv-layout.yaml        |   2 +-
 .../bindings/nvmem/qcom,qfprom.yaml           |   7 +-
 Documentation/driver-api/nvmem.rst            |  15 +
 MAINTAINERS                                   |  12 +
 drivers/nvmem/Kconfig                         |  14 +
 drivers/nvmem/Makefile                        |   2 +
 drivers/nvmem/core.c                          | 283 ++++++++++++-----
 drivers/nvmem/imx-ocotp.c                     |  34 +-
 drivers/nvmem/layouts/Kconfig                 |  23 ++
 drivers/nvmem/layouts/Makefile                |   7 +
 drivers/nvmem/layouts/onie-tlv.c              | 244 ++++++++++++++
 drivers/nvmem/layouts/sl28vpd.c               | 153 +++++++++
 drivers/nvmem/qcom-spmi-sdam.c                |  13 +-
 drivers/nvmem/rave-sp-eeprom.c                |   2 +-
 drivers/nvmem/stm32-bsec-optee-ta.c           | 298 ++++++++++++++++++
 drivers/nvmem/stm32-bsec-optee-ta.h           |  80 +++++
 drivers/nvmem/stm32-romem.c                   |  84 ++++-
 drivers/nvmem/sunxi_sid.c                     |   8 +-
 drivers/of/property.c                         |   6 +-
 include/linux/etherdevice.h                   |  14 +
 include/linux/nvmem-consumer.h                |  17 +-
 include/linux/nvmem-provider.h                |  95 +++++-
 include/linux/of.h                            |  25 ++
 23 files changed, 1310 insertions(+), 128 deletions(-)
 create mode 100644 drivers/nvmem/layouts/Kconfig
 create mode 100644 drivers/nvmem/layouts/Makefile
 create mode 100644 drivers/nvmem/layouts/onie-tlv.c
 create mode 100644 drivers/nvmem/layouts/sl28vpd.c
 create mode 100644 drivers/nvmem/stm32-bsec-optee-ta.c
 create mode 100644 drivers/nvmem/stm32-bsec-optee-ta.h

Comments

Greg KH Jan. 28, 2023, 1:43 p.m. UTC | #1 
On Fri, Jan 27, 2023 at 11:15:28AM +0000, Srinivas Kandagatla wrote:
> Hi Greg,
> 
> Here are some nvmem patches bit more than usual for 6.3 which includes
> 
> - Adding support for nvmem layouts, thanks to Michael and Miquel for
>   driving this effort.
> - Add support to stm32 STM32MP15x OPTEE based nvmem provider
> - Updated to qfprom bindings to include various Qualcomm SoCs.
> - adding sl28vpd provider layout
> - move imx provider to use new layout apis
> - add ONIE provider layout. 
> - new helper eth_addr_add().
> - few minor enhancements to core and providersdrivers.
> 
> Can you please queue them up for 6.3.

This series does NOT apply to my char-misc-next branch, which is based
on 6.2-rc5.  What did you generate it against?

Can you rebase it and resend?

thanks,

greg k-h
Srinivas Kandagatla Jan. 30, 2023, 11:27 a.m. UTC | #2 
On 28/01/2023 13:43, Greg KH wrote:
> On Fri, Jan 27, 2023 at 11:15:28AM +0000, Srinivas Kandagatla wrote:
>> Hi Greg,
>>
>> Here are some nvmem patches bit more than usual for 6.3 which includes
>>
>> - Adding support for nvmem layouts, thanks to Michael and Miquel for
>>    driving this effort.
>> - Add support to stm32 STM32MP15x OPTEE based nvmem provider
>> - Updated to qfprom bindings to include various Qualcomm SoCs.
>> - adding sl28vpd provider layout
>> - move imx provider to use new layout apis
>> - add ONIE provider layout.
>> - new helper eth_addr_add().
>> - few minor enhancements to core and providersdrivers.
>>
>> Can you please queue them up for 6.3.
> 
> This series does NOT apply to my char-misc-next branch, which is based
> on 6.2-rc5.  What did you generate it against?
> 
These were on top of nvmem-fixes based on 6.2-rc1.


> Can you rebase it and resend?

char-misc-next does not have nvmem-fixes yet, which branch should I 
rebase these on?

thanks,
srini

> 
> thanks,
> 
> greg k-h
Greg KH Jan. 30, 2023, 11:59 a.m. UTC | #3 
On Mon, Jan 30, 2023 at 11:27:06AM +0000, Srinivas Kandagatla wrote:
> 
> 
> On 28/01/2023 13:43, Greg KH wrote:
> > On Fri, Jan 27, 2023 at 11:15:28AM +0000, Srinivas Kandagatla wrote:
> > > Hi Greg,
> > > 
> > > Here are some nvmem patches bit more than usual for 6.3 which includes
> > > 
> > > - Adding support for nvmem layouts, thanks to Michael and Miquel for
> > >    driving this effort.
> > > - Add support to stm32 STM32MP15x OPTEE based nvmem provider
> > > - Updated to qfprom bindings to include various Qualcomm SoCs.
> > > - adding sl28vpd provider layout
> > > - move imx provider to use new layout apis
> > > - add ONIE provider layout.
> > > - new helper eth_addr_add().
> > > - few minor enhancements to core and providersdrivers.
> > > 
> > > Can you please queue them up for 6.3.
> > 
> > This series does NOT apply to my char-misc-next branch, which is based
> > on 6.2-rc5.  What did you generate it against?
> > 
> These were on top of nvmem-fixes based on 6.2-rc1.

Ah, always say that please.

> > Can you rebase it and resend?
> 
> char-misc-next does not have nvmem-fixes yet, which branch should I rebase
> these on?

char-misc-next please.  If there are going to be merge conflicts when
the char-misc-linus branch gets merged into that with these changes,
please let me know.

thanks,

greg k-h
Srinivas Kandagatla Jan. 30, 2023, 3:54 p.m. UTC | #4 
On 30/01/2023 11:59, Greg KH wrote:
> On Mon, Jan 30, 2023 at 11:27:06AM +0000, Srinivas Kandagatla wrote:
>>
>>
>> On 28/01/2023 13:43, Greg KH wrote:
>>> On Fri, Jan 27, 2023 at 11:15:28AM +0000, Srinivas Kandagatla wrote:
>>>> Hi Greg,
>>>>
>>>> Here are some nvmem patches bit more than usual for 6.3 which includes
>>>>
>>>> - Adding support for nvmem layouts, thanks to Michael and Miquel for
>>>>     driving this effort.
>>>> - Add support to stm32 STM32MP15x OPTEE based nvmem provider
>>>> - Updated to qfprom bindings to include various Qualcomm SoCs.
>>>> - adding sl28vpd provider layout
>>>> - move imx provider to use new layout apis
>>>> - add ONIE provider layout.
>>>> - new helper eth_addr_add().
>>>> - few minor enhancements to core and providersdrivers.
>>>>
>>>> Can you please queue them up for 6.3.
>>>
>>> This series does NOT apply to my char-misc-next branch, which is based
>>> on 6.2-rc5.  What did you generate it against?
>>>
>> These were on top of nvmem-fixes based on 6.2-rc1.
> 
> Ah, always say that please.
My bad, I assumed that fixes will be applied and then these patches. But 
I should have mentioned this clearly.

> 
>>> Can you rebase it and resend?
>>
>> char-misc-next does not have nvmem-fixes yet, which branch should I rebase
>> these on?
> 
> char-misc-next please.  If there are going to be merge conflicts when
> the char-misc-linus branch gets merged into that with these changes, > please let me know.

Yes, for sure this is going to conflict. some of the patches in this set 
are on top of fixes.


--srini


> 
> thanks,
> 
> greg k-h
Greg KH Feb. 6, 2023, 7:45 a.m. UTC | #5 
On Mon, Jan 30, 2023 at 03:54:58PM +0000, Srinivas Kandagatla wrote:
> 
> 
> On 30/01/2023 11:59, Greg KH wrote:
> > On Mon, Jan 30, 2023 at 11:27:06AM +0000, Srinivas Kandagatla wrote:
> > > 
> > > 
> > > On 28/01/2023 13:43, Greg KH wrote:
> > > > On Fri, Jan 27, 2023 at 11:15:28AM +0000, Srinivas Kandagatla wrote:
> > > > > Hi Greg,
> > > > > 
> > > > > Here are some nvmem patches bit more than usual for 6.3 which includes
> > > > > 
> > > > > - Adding support for nvmem layouts, thanks to Michael and Miquel for
> > > > >     driving this effort.
> > > > > - Add support to stm32 STM32MP15x OPTEE based nvmem provider
> > > > > - Updated to qfprom bindings to include various Qualcomm SoCs.
> > > > > - adding sl28vpd provider layout
> > > > > - move imx provider to use new layout apis
> > > > > - add ONIE provider layout.
> > > > > - new helper eth_addr_add().
> > > > > - few minor enhancements to core and providersdrivers.
> > > > > 
> > > > > Can you please queue them up for 6.3.
> > > > 
> > > > This series does NOT apply to my char-misc-next branch, which is based
> > > > on 6.2-rc5.  What did you generate it against?
> > > > 
> > > These were on top of nvmem-fixes based on 6.2-rc1.
> > 
> > Ah, always say that please.
> My bad, I assumed that fixes will be applied and then these patches. But I
> should have mentioned this clearly.
> 
> > 
> > > > Can you rebase it and resend?
> > > 
> > > char-misc-next does not have nvmem-fixes yet, which branch should I rebase
> > > these on?
> > 
> > char-misc-next please.  If there are going to be merge conflicts when
> > the char-misc-linus branch gets merged into that with these changes, > please let me know.
> 
> Yes, for sure this is going to conflict. some of the patches in this set are
> on top of fixes.

Ok, now that the char-misc-linus branch is merged into my -next branch,
I've applied these.

thanks,

greg k-h
Greg KH Feb. 6, 2023, 7:46 a.m. UTC | #6 
On Mon, Feb 06, 2023 at 08:45:29AM +0100, Greg KH wrote:
> On Mon, Jan 30, 2023 at 03:54:58PM +0000, Srinivas Kandagatla wrote:
> > 
> > 
> > On 30/01/2023 11:59, Greg KH wrote:
> > > On Mon, Jan 30, 2023 at 11:27:06AM +0000, Srinivas Kandagatla wrote:
> > > > 
> > > > 
> > > > On 28/01/2023 13:43, Greg KH wrote:
> > > > > On Fri, Jan 27, 2023 at 11:15:28AM +0000, Srinivas Kandagatla wrote:
> > > > > > Hi Greg,
> > > > > > 
> > > > > > Here are some nvmem patches bit more than usual for 6.3 which includes
> > > > > > 
> > > > > > - Adding support for nvmem layouts, thanks to Michael and Miquel for
> > > > > >     driving this effort.
> > > > > > - Add support to stm32 STM32MP15x OPTEE based nvmem provider
> > > > > > - Updated to qfprom bindings to include various Qualcomm SoCs.
> > > > > > - adding sl28vpd provider layout
> > > > > > - move imx provider to use new layout apis
> > > > > > - add ONIE provider layout.
> > > > > > - new helper eth_addr_add().
> > > > > > - few minor enhancements to core and providersdrivers.
> > > > > > 
> > > > > > Can you please queue them up for 6.3.
> > > > > 
> > > > > This series does NOT apply to my char-misc-next branch, which is based
> > > > > on 6.2-rc5.  What did you generate it against?
> > > > > 
> > > > These were on top of nvmem-fixes based on 6.2-rc1.
> > > 
> > > Ah, always say that please.
> > My bad, I assumed that fixes will be applied and then these patches. But I
> > should have mentioned this clearly.
> > 
> > > 
> > > > > Can you rebase it and resend?
> > > > 
> > > > char-misc-next does not have nvmem-fixes yet, which branch should I rebase
> > > > these on?
> > > 
> > > char-misc-next please.  If there are going to be merge conflicts when
> > > the char-misc-linus branch gets merged into that with these changes, > please let me know.
> > 
> > Yes, for sure this is going to conflict. some of the patches in this set are
> > on top of fixes.
> 
> Ok, now that the char-misc-linus branch is merged into my -next branch,
> I've applied these.

Nope, lots of errors:

Commit: b4fee523c0d7 ("nvmem: stm32: fix OPTEE dependency")
	Fixes tag: Fixes: ae46fd89cc0cc ("nvmem: stm32: add OP-TEE support for STM32MP13x")
	Has these problem(s):
		- Target SHA1 does not exist
Commit: b6dc9d9a156a ("of: property: fix #nvmem-cell-cells parsing")
	Fixes tag: Fixes: 6a80b3e6fb41 ("of: property: make #.*-cells optional for simple props")
	Has these problem(s):
		- Target SHA1 does not exist
Commit: 57a71161cecb ("nvmem: core: fix nvmem_layout_get_match_data()")
	Fixes tag: Fixes: f61a093b4a0e ("nvmem: core: introduce NVMEM layouts")
	Has these problem(s):
		- Target SHA1 does not exist
Commit: 8e1cd6f05f71 ("nvmem: core: return -ENOENT if nvmem cell is not found")
	Fixes tag: Fixes: e894d5ad177c ("nvmem: core: add an index parameter to the cell")
	Has these problem(s):
		- Target SHA1 does not exist


Can you please fix this up and resend?

thanks,

greg k-h
Srinivas Kandagatla Feb. 6, 2023, 10:13 a.m. UTC | #7 
On 06/02/2023 07:46, Greg KH wrote:
> On Mon, Feb 06, 2023 at 08:45:29AM +0100, Greg KH wrote:
>> On Mon, Jan 30, 2023 at 03:54:58PM +0000, Srinivas Kandagatla wrote:
>>>
>>>
>>> On 30/01/2023 11:59, Greg KH wrote:
>>>> On Mon, Jan 30, 2023 at 11:27:06AM +0000, Srinivas Kandagatla wrote:
>>>>>
>>>>>
>>>>> On 28/01/2023 13:43, Greg KH wrote:
>>>>>> On Fri, Jan 27, 2023 at 11:15:28AM +0000, Srinivas Kandagatla wrote:
>>>>>>> Hi Greg,
>>>>>>>
>>>>>>> Here are some nvmem patches bit more than usual for 6.3 which includes
>>>>>>>
>>>>>>> - Adding support for nvmem layouts, thanks to Michael and Miquel for
>>>>>>>      driving this effort.
>>>>>>> - Add support to stm32 STM32MP15x OPTEE based nvmem provider
>>>>>>> - Updated to qfprom bindings to include various Qualcomm SoCs.
>>>>>>> - adding sl28vpd provider layout
>>>>>>> - move imx provider to use new layout apis
>>>>>>> - add ONIE provider layout.
>>>>>>> - new helper eth_addr_add().
>>>>>>> - few minor enhancements to core and providersdrivers.
>>>>>>>
>>>>>>> Can you please queue them up for 6.3.
>>>>>>
>>>>>> This series does NOT apply to my char-misc-next branch, which is based
>>>>>> on 6.2-rc5.  What did you generate it against?
>>>>>>
>>>>> These were on top of nvmem-fixes based on 6.2-rc1.
>>>>
>>>> Ah, always say that please.
>>> My bad, I assumed that fixes will be applied and then these patches. But I
>>> should have mentioned this clearly.
>>>
>>>>
>>>>>> Can you rebase it and resend?
>>>>>
>>>>> char-misc-next does not have nvmem-fixes yet, which branch should I rebase
>>>>> these on?
>>>>
>>>> char-misc-next please.  If there are going to be merge conflicts when
>>>> the char-misc-linus branch gets merged into that with these changes, > please let me know.
>>>
>>> Yes, for sure this is going to conflict. some of the patches in this set are
>>> on top of fixes.
>>
>> Ok, now that the char-misc-linus branch is merged into my -next branch,
>> I've applied these.
> 
> Nope, lots of errors:
> 
> Commit: b4fee523c0d7 ("nvmem: stm32: fix OPTEE dependency")
> 	Fixes tag: Fixes: ae46fd89cc0cc ("nvmem: stm32: add OP-TEE support for STM32MP13x")
> 	Has these problem(s):
> 		- Target SHA1 does not exist
> Commit: b6dc9d9a156a ("of: property: fix #nvmem-cell-cells parsing")
> 	Fixes tag: Fixes: 6a80b3e6fb41 ("of: property: make #.*-cells optional for simple props")
> 	Has these problem(s):
> 		- Target SHA1 does not exist
> Commit: 57a71161cecb ("nvmem: core: fix nvmem_layout_get_match_data()")
> 	Fixes tag: Fixes: f61a093b4a0e ("nvmem: core: introduce NVMEM layouts")
> 	Has these problem(s):
> 		- Target SHA1 does not exist
> Commit: 8e1cd6f05f71 ("nvmem: core: return -ENOENT if nvmem cell is not found")
> 	Fixes tag: Fixes: e894d5ad177c ("nvmem: core: add an index parameter to the cell")
> 	Has these problem(s):
> 		- Target SHA1 does not exist
> 
> 
> Can you please fix this up and resend?
> 
thanks Greg for trying out.
Sure, will rebase on top of char-misc-next

--srini
> thanks,
> 
> greg k-h