regmap: permit to set reg_update_bits with bulk implementation
Subsystems (2)
PATCH 1/1 regmap: permit to set reg_update_bits with bulk implementation
A regmap may still require to set a custom reg_update_bits instead of relying to the regmap_bus_read/write general function.
Permit to set it in the map if provided by the regmap config.
---
If this is accepted, this is needed for net-next tree so a signed tags is needed, if it's not a problem.
drivers/base/regmap/regmap.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/base/regmap/regmap.c +2 -0
@@ -882,6 +882,8 @@ struct regmap *__regmap_init(struct device *dev,if (config && config->read && config->write) { map->reg_read = _regmap_bus_read; +if (config->reg_update_bits) + map->reg_update_bits = config->reg_update_bits;/* Bulk read/write */ map->read = config->read;
Signature · 1 line
2.36.1
Mark Brown
maintainerQuoted 6 lines · Christian Marangi
A regmap may still require to set a custom
reg_update_bitsinstead of relying to the regmap_bus_read/write general function.Permit to set it in the map if provided by the regmap config.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next
Thanks!
[1/1] regmap: permit to set reg_update_bits with bulk implementation
commit: 739f872e48d47c97fa17a86a7b3356771b75240c
All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying to this mail.
Thanks,
Mark
Quoted 8 lines · Mark Brown
Quoted 6 lines · Christian Marangi
A regmap may still require to set a custom
reg_update_bitsinstead of relying to the regmap_bus_read/write general function.Permit to set it in the map if provided by the regmap config.
Quoted 9 lines
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next
Thanks!
[1/1] regmap: permit to set
reg_update_bitswith bulk implementationcommit: 739f872e48d47c97fa17a86a7b3356771b75240c
Hi,
thanks, assuming everything went smooth with the merge to linux-next and no problems arise, can you provide a signed tag?
This is needed for a net-next series that is currently in RFC state as it does depends on this.
(I had this problem before and it was said that in this kind of situation I had to ask for a signed tag to merge the related patch in net-next branch)
Thanks for the help!
Signature · 1 line
Ansuel
Mark Brown
maintainerQuoted 9 lines · Christian Marangi
thanks, assuming everything went smooth with the merge to linux-next and no problems arise, can you provide a signed tag?
This is needed for a net-next series that is currently in RFC state as it does depends on this.
(I had this problem before and it was said that in this kind of situation I had to ask for a signed tag to merge the related patch in net-next branch)
Oh, it would have been good to know about this when reviewing the patch rather than after the fact - since this hadn't been mentioned it's now applied on the main development branch with everything that's going into the next release rather than on a separate branch for easy merging elsewhere. How urgent is this, given that the merge window is likely to open at the weekend so this'll get sent to Linus at that point - is the driver otherwise near merging?
Quoted 12 lines · Mark Brown
Quoted 9 lines · Christian Marangi
thanks, assuming everything went smooth with the merge to linux-next and no problems arise, can you provide a signed tag?
This is needed for a net-next series that is currently in RFC state as it does depends on this.
(I had this problem before and it was said that in this kind of situation I had to ask for a signed tag to merge the related patch in net-next branch)
Quoted 7 lines
Oh, it would have been good to know about this when reviewing the patch rather than after the fact - since this hadn't been mentioned it's now applied on the main development branch with everything that's going into the next release rather than on a separate branch for easy merging elsewhere. How urgent is this, given that the merge window is likely to open at the weekend so this'll get sent to Linus at that point - is the driver otherwise near merging?
Ohh sorry, I was too generic in the patch comments and didn't mention it was an actual dependency.
It's not too urgent, (I assume) but it was said that it was preferrable to have the changes done in 2 weeks window (the one in net-next about the working driver). Will ask on net-next and give you news ASAP.
Signature · 1 line
Ansuel
Quoted 21 lines · Christian Marangi
Quoted 12 lines · Mark Brown
Quoted 9 lines · Christian Marangi
thanks, assuming everything went smooth with the merge to linux-next and no problems arise, can you provide a signed tag?
This is needed for a net-next series that is currently in RFC state as it does depends on this.
(I had this problem before and it was said that in this kind of situation I had to ask for a signed tag to merge the related patch in net-next branch)
Quoted 7 lines
Oh, it would have been good to know about this when reviewing the patch rather than after the fact - since this hadn't been mentioned it's now applied on the main development branch with everything that's going into the next release rather than on a separate branch for easy merging elsewhere. How urgent is this, given that the merge window is likely to open at the weekend so this'll get sent to Linus at that point - is the driver otherwise near merging?
Quoted 7 lines
Ohh sorry, I was too generic in the patch comments and didn't mention it was an actual dependency.
It's not too urgent, (I assume) but it was said that it was preferrable to have the changes done in 2 weeks window (the one in net-next about the working driver). Will ask on net-next and give you news ASAP.
Hi Mark,
sorry for the delay, I pointed out this problem with net-next and we decided to adopt a workaround so this is not urgent anymore and we can wait the merge window to have this change in net-next.
The required code will be updated later when this change is merged.
Signature · 1 line
Ansuel